W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2017

[csswg-drafts] [css-display][css-flexbox] Contradictory definitions of block-level

From: Loirooriol via GitHub <sysbot+gh@w3.org>
Date: Wed, 05 Apr 2017 22:40:19 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-219736206-1491432017-sysbot+gh@w3.org>
Loirooriol has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-display][css-flexbox] Contradictory definitions of block-level ==
[CSS Flexbox](https://drafts.csswg.org/css-flexbox/#flex-items) says

> flex items themselves are *flex-level* boxes, not block-level boxes: they participate in their container’s flex formatting context, not in a block formatting context.

This seems to mean that participating in a block formatting context is a requirement for being block-level.

However, [CSS Display](https://drafts.csswg.org/css-display/#outer-role) says otherwise:

>The <display-outside> keywords specify the element’s outer display type, which is essentially its role in flow layout. They are defined as follows:
> - `block`: The element generates a block-level box.

Then, having a `block` outer display type is enough to be block-level.

Since flex items are blockified, they always have a `block` outer display type. So they are block-level.

This contradicts the first quote.




Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1175 using your GitHub account
Received on Wednesday, 5 April 2017 22:40:26 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:11 UTC