> I think gap is where this is all headed in the long term. gap? Is this new? I've been waiting for years for CSS to finally support something like that. Always thought it was weird that I had to mess with margins (and last-child hacks) to get a proper gap between items in a container.
You want enabling CSS selectors, not disabling ones
11–20 of 120 posts
Re: You want enabling CSS selectors, not disabling ones
#12> I think gap is where this is all headed in the long term. gap? Is this new? I've been waiting for years for CSS to finally support something like that. Always thought it was weird that I had to mess with margins (and last-child hacks) to get a proper gap between items in a container.
It's part of CSS grid so in a way it's new, but CSS grid well supported nowadays.
Re: You want enabling CSS selectors, not disabling ones
#13> I think gap is where this is all headed in the long term. gap? Is this new? I've been waiting for years for CSS to finally support something like that. Always thought it was weird that I had to mess with margins (and last-child hacks) to get a proper gap between items in a container.
It's part of CSS grid so in a way it's new, but CSS grid well supported nowadays.
It's been made more general than just grid (it used to be called grid-gap) and works with flexbox too. I don't know if Safari supports it in flexbox yet and it's a pain to detect with @supports because Safari _does_ support gap but in a different context, but it works fine in Chrome and Firefox.
Edit: just checked, Safari 14.1 added support for using gap with Flexbox.
Re: You want enabling CSS selectors, not disabling ones
#14> I think gap is where this is all headed in the long term. gap? Is this new? I've been waiting for years for CSS to finally support something like that. Always thought it was weird that I had to mess with margins (and last-child hacks) to get a proper gap between items in a container.
It's part of CSS grid so in a way it's new, but CSS grid well supported nowadays.
[deleted]
Re: You want enabling CSS selectors, not disabling ones
#15Interesting way to think – we use additive color (RGB) on web so why not additive styling?
But in practice while creating interfaces, we're making broad brush strokes, then accommodating exceptions, like :last-child.
Also curious about how browsers prioritize the render stages – does every style get applied sequentially (hence cascading), or do pseudo selectors get applied later during the paint?
Re: You want enabling CSS selectors, not disabling ones
#16I don't see why 0 should be treated as special value. Initial should be used if meant to "disable" it. What if you want margin: 5px as the general rule and margin: 10px on the last element. Is 10px a disabling selector?
I believe that's exactly the point. You don't set all to 5px and then override using a special rule that says 0px for the last. You exclude the last element from the 5px rule. There might be other rules, browser, user that should not over the 5px rule
I disagree. If a 5px margin is the general rule, then I would argue it's cleaner to apply it generally, and then apply the 10px margin exceptions in separate rules.
- When special cases are added or removed, the general rule won't have to be adjusted, just code that handles the special cases.
- On the other hand, a single general rule that specifically avoids application to multiple exceptional cases will be pretty long and have multiple :not()s, thus reducing readability and maintainability.
Why burden the general rule with knowledge of its exceptions? To me, doing so is a (small) violation of the principle of separation of concerns.
Re: You want enabling CSS selectors, not disabling ones
#17I had a sore throat, so I made an "In A World" reading of this web page.
Re: You want enabling CSS selectors, not disabling ones
#18Interesting way to think – we use additive color (RGB) on web so why not additive styling? But in practice while creating interfaces, we're making broad brush strokes, then accommodating exceptions, like :last-child. Also curious about how browsers prioritize the render stages – does every style get applied sequentially (hence cascading), or do pseudo selectors get applied later during the paint?
Style calculations are typically done before rendering, but as far as I know, there's nothing in the spec that dictates you needing to do anything specific other than comply with the output outlined.
Re: You want enabling CSS selectors, not disabling ones
#19Is there a language that compiles to CSS but excludes the decades of cruft that have accumulated in CSS? Something that just exposes a few key primitives and jettisons the rest even if that means it doesn't handle some extreme edge cases?
Re: You want enabling CSS selectors, not disabling ones
#20Earlier quoted context omitted.
I believe that's exactly the point. You don't set all to 5px and then override using a special rule that says 0px for the last. You exclude the last element from the 5px rule. There might be other rules, browser, user that should not over the 5px rule
I disagree. If a 5px margin is the general rule, then I would argue it's cleaner to apply it generally, and then apply the 10px margin exceptions in separate rules. - When special cases are added or removed, the general rule won't have to be adjusted, just code that handles the special cases. - On the other hand, a single general rule that specifically avoids application to multiple exceptional cases will be pretty l…
plus it's called "cascading style sheets". you're going against the current if everything wants to be so specific. This is one of my gripes with styled components.. it makes it easy to forget the power of cascading rules!