-
Notifications
You must be signed in to change notification settings - Fork 106
#issue-360: resolve grid gap issue wtth band body #361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…nd simplify selectors. Add extra bootstrap cruft to demo
|
I was already planning to deprecate the slot mixin. The goal behind was not to simplify the code but rather, slots are really confusing about how to structure the selector so the goal was to abstract that so that if we find a better way to structure our slotted references, we could update that in the mixin and have it propagate everywhere. That said, I just couldn't make the mixin work well. |
|
So +1 slot mixin deprecation but I'd push back on removing all the loops from our sass like this. It's not that much abstraction to say, for the following regions - header, footer, body, aside - do this same thing. |
|
@castastrophe when I was trying to add the fallback margins and test in IE11, I noticed two things:
#1 has major implications in terms of how we style things and how they work (or don't in IE11) if that is true. cc @markcaron @kylebuch8 |
this is what the band looks like in IE11, when i can get it to load (after i added the band, the page throws errors about a script taking too long to load) |
…band body), update readme with explicit notes for this section, refine demo file
…fork Proposed optimization, returns some of the formatting and tooling
castastrophe
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a couple of documentation notes, otherwise great +1!
…patternfly-elements into issue-360/band-body-grid-gap
castastrophe
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
When trying to unravel issue #360, I noticed that in the band component, the compiled css contained this style:
which (I think?) is coming from this sass:
which lead me to wonder, is there much to gain from abstracting selectors? I was searching and searching for
slottedbut couldn't find it because it was@include pfe-slot()instead. So I thought maybe this is one of the levels of abstraction we can simplify? I understand the looping was to reduce replicating code, but it was also generating css selectors that don't work:::slotted([slot="pfe-band--header"] > *:not(:last-child)). Side note for the future, this selector (line 59) does work:[name="title"]::slotted(*:not(:last-of-type))So, the explanation is almost longer than the code, but I wanted to explain the why for this approach, and why I removed the slot mixin. :)