earlier replies
Replying to @SaraSoueidan
I use what works but aim to make the platform generally better so we don’t have to do this stuff in future …
2
1
… think sometimes the hacks indicate a use case for something we actually need in CSS.
1
3
Indeed. I said I'd file an issue @csswg for this so that maybe the future would make it simpler. I think the hack is horrible.
1
cool :) I’d love to see what it is you are talking about
1
2
Me too. I'm completely intrigued now!
1
1
It's basically: floating, clearing floats and still not allowing content to break even when it does. :D
2
I'd be curious to read the 4-tweet explanation of that, since I didn't understand the 1-tweet one.
1
We're doing a case study + talk on the entire project in a few weeks which will include that :)
1
In short: I have 3 floated divs, one non-floated "floating" beside those, & when I float smth inside div#4
1
that div is cleared (for some magical reason) so it no longer "flows" next to the previous 3. o.0
2
Replying to @SaraSoueidan @zomigi @rachelandrew
Was this rule #5 in drafts.csswg.org/css2/visure… or something more complicated?

Aug 16, 2016 · 5:28 AM UTC

1
Replying to @davidbaron @zomigi @rachelandrew
Yes BUT the div wasn't initially floated so this shouldn't have happened. It only happened when an [1/2]
1
element inside of that div was floated—which is what confused me. [2/2]
2