the unofficial sequel to my CSS shapes article written more than 3 years ago. let's talk a bit about CSS exclusions (and also, specifications, and building demos, and raising bugs)
#webdev #css
bit.ly/bey-exclusions
1
7
2
22
For what it's worth, my basic argument against the current exclusions proposal is that they promote the opposite of responsive design: design that's fragile and breaks in response to slight changes in viewport size, fonts, or other variables.
1
2
I think that in order for an exclusions model to be responsive, the rules for placement of the exclusions need to have a collision handling model, so that the way you place exclusions involves rules for how to move the exclusion if you put two in the same place.
1
3
Floats have this, but absolute positioning doesn't.
And I think it's particularly bad in paginated contexts, which is where most of the demos of exclusions focused.
1
1
A collision handling model could involve defaults (like floats), or it could involve a way to specify the collision handling behavior in some way.
But overlap by default is not a good behavior.
1
1
There it's "always overlap" rather than "sometimes overlap as a function of lots of variables", right? (Or did I miss something?) So it's much more clearly an intentional choice to overlap.
Jul 31, 2018 · 5:10 AM UTC
1


