Re: [csswg-drafts] [css-contain-2] contain:size shouldn't fragment as monolithic (#5648)

> <chrishtr> iank_: in some cases Chromium is the only implementation that treats break-inside as non-monolithic. advised people to use contain: size for some cases.
[...]
> <dholbert> correcting earlier notes, iank had actually said "Chromium is the only implementation to treat `break-inside:avoid` as monolithic"

Sorry, my last-minute correction^ (attempting to answer [an emote-question from @fantasai](https://log.csswg.org/irc.w3.org/css/2024-06-26/#e1633464)) was misguided.  After the meeting ended, @bfgeek (iank) [mentioned that he did actually mean **non-monolithic**](https://log.csswg.org/irc.w3.org/css/2024-06-26/#e1633486)

@bfgeek: question for you -- do you have a testcase to demonstrate what you're talking about there? (sorry for the diversion; it seems sorta-relevant since `break-inside:avoid` is kind-of like the behavior that @frivoal is suggesting here.)

I tested Firefox vs. Chrome on these testcases:

block:
`data:text/html,Hello<div style="break-inside:avoid; border: 10px solid black;font:6in monospace">A<br>B<br>C`

flex:
`data:text/html,Hello<div style="display:flex;flex-direction:column;break-inside:avoid; border: 10px solid black;font:6in monospace"><div>A</div><div>B</div><div>C</div>`

...and both Firefox and Chrome push the div to the second page, but don't slice it.  So we're both treating it as sort-of-but-not-quite-monotonic, in the same way. :)  Could you clarify what situation you're talking about where Chrome is the only engine to do  the right non-monotonic thing with `break-inside:avoid`?

-- 
GitHub Notification of comment by dholbert
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5648#issuecomment-2192819129 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 27 June 2024 00:07:26 UTC