- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 May 2017 00:45:47 +0000
- To: public-css-archive@w3.org
So the core point of inlinification is to ensure that nothing can break the inline context it's working in. "block flow-root" elements become "inline flow-root" ("inline-block"), which is fine - they're atomic inlines. But "block flow" naively becomes "inline flow", which still allows descendant blocks to bubble up a break.
The current text solves this by recursing, so that a "block flow" becomes "inline flow", then its children inlinify as well, ensuring there's no visible block descendants.
Instead turning "block flow" into "inline flow-root" also solves this, by hiding any descendant blocks.
Either solution solves the problem. Are there any good use-cases suggesting that we go for one vs the other?
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1341#issuecomment-301643544 using your GitHub account
Received on Tuesday, 16 May 2017 00:45:58 UTC