W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2019

[csswg-drafts] [css-display] editorial: blockification/inlinification of list-items (#4000)

From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
Date: Tue, 04 Jun 2019 01:12:33 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-451752685-1559610752-sysbot+gh@w3.org>
MatsPalmgren has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-display] editorial: blockification/inlinification of list-items ==
https://drafts.csswg.org/css-display/#transformations
First bullet says: "If a `block flow` box is inlinified...". Technically, that excludes `block flow list-item`, however it probably should include it so that it remains a block container too. I.e. the value should become `inline flow-root list-item` rather than `inline flow list-item`, which is what the spec currently says. (You might want to use the term "block box" instead of the explicit `display` value to include list-items.)

Second bullet says: "If an `inline flow` box is inlinified..." should perhaps also include `inline flow list-item`? (Could use the term "inline box" here.)

Third bullet: "For legacy reasons, if an `inline flow-root` box (aka inline-block) is blockified, it becomes a block box (losing its `flow-root` nature). For consistency, a `run-in flow-root` box also blockifies to a block box." I don't think any UAs  support inline list-items yet, so there's no legacy to care about here, but given that `run-in flow-root` (also not supported yet) also does this then `inline flow-root list-item` should probably also be included here (i.e. it becomes `block flow list-item`).


Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4000 using your GitHub account
Received on Tuesday, 4 June 2019 01:12:35 UTC

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