Re: [csswg-drafts] [css-display] 'flow' inner display type should never establish a BFC

It's acceptable, but in fact I no longer have a strong opinion about this. I wanted the `flow` inner display type to never establish a BFC, and explain the cases in which a BFC is needed by saying that the used `display` value of the generating element has been changed to `flow-root`.

But this does not work well for `display: block ruby`, because the principal box may need a BFC due to e.g. `overflow: hidden`. I wanted to address this with a new `ruby-root` inner display type (#1700), which was rejected. This means that the establishment of a BFC can't be explained (not exclusively, at least) in terms of the element's display type.

Then, I don't mind noting that if an element with `flow` inner display type generates a block container that establishes a BFC, the result looks like if the element had a `flow-root` inner display type. But this doesn't seem to simplify things, which is what I initially wanted.

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

Received on Monday, 7 May 2018 19:41:30 UTC