- From: Oriol via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Aug 2017 15:29:56 +0000
- To: public-css-archive@w3.org
Loirooriol has just created a new issue for https://github.com/w3c/csswg-drafts:
== [css-display][css-tables][css-flexbox][css-grid] 'block' outer display type does not always produce a block-level ==
[CSS Tables](https://drafts.csswg.org/css-tables-3/#table) says that `table` generates a block-level table.
[CSS Flexbox](https://drafts.csswg.org/css-flexbox/#valdef-display-flex) says that `flex` generates a block-level flex container.
[CSS Grid](https://drafts.csswg.org/css-grid/#valdef-display-grid) says that `grid` generates a block-level grid container.
[CSS Display](https://drafts.csswg.org/css-display-3/#ref-for-valdef-display-block) says the above plus things like that `block` generates a block box.
However, this is only true in flow layout. Outside of flow layout, the `block` outer display type can also generate a flex-level or grid-level principal box.
I think there are two reasonable solutions:
- Say that "flex-level" and "grid-level" are sublevels of "block-level" instead of entirely different things. So we could say e.g. that a flex item is both flex-level and block-level, but a block box in flow layout is only block-level.
I think this would only require editing the text in CSS Flexbox and CSS Grid which says that flex items and grid items are not block-level.
- Define a new term called "blocklike-level", "normal-level", "auto-level" or similar which is defined as such:
- Inside flow layout, a synonym for "block-level".
- Inside flex layout, a synonym for "flex-level".
- Inside flex layout, a synonym for "grid-level".
And then update the specs to use that term instead of "block-level" when necessary. I prefer this option, but it's more work.
In both cases it would be a good idea to define all the possible box levels in CSS Display.
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1704 using your GitHub account
Received on Monday, 7 August 2017 15:30:01 UTC