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

CSS exclusions with Queen Bey

I recently came across a post by Ben Frain expressing his frustrations about CSS shapes and exclusions. And although I can see where he is coming from (he made that pretty clear in his examples), I...

chenhuijing.com
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
Replying to @davidbaron @hj_chen
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.

Jul 31, 2018 · 4:00 AM UTC

1
1
Replying to @davidbaron @hj_chen
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
more replies