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

[csswg-drafts] [css-display][css-ruby] Inlinification Considerations

From: fantasai via GitHub <sysbot+gh@w3.org>
Date: Wed, 17 May 2017 22:18:34 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-229503406-1495059512-sysbot+gh@w3.org>
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-display][css-ruby] Inlinification Considerations ==
Inlinification (such as what happens to the block-level contents of a run-in or ruby annotation) currently doesn't affect the display of layout-internal types like `table-row`: for these boxes no computed value `display` alteration happens, and anonymous box fixup will wrap them accordingly. Blockification instead converts the display value to `block` (so no anonymous box fixup happens, and also any further structure inside it is disrupted by the conversion to `block`). Is there a reason to do one vs the other here?

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1390 using your GitHub account
Received on Wednesday, 17 May 2017 22:18:41 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 10:12:53 UTC