- From: Loirooriol via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Jun 2017 21:55:12 +0000
- To: public-css-archive@w3.org
> This also avoids adding `flow-root` to the other display-inside values, where it's meaningless. Useless for table, flex and grid, yes. But I don't think it's useless for ruby. Something needs to be done with ruby when it becomes a formatting context, e.g. it has `contain: layout` (#1457). I think this could be manually triggered with `flow-root`. --- Just to be sure I understand, you are proposing something the following, right? | Full | Short | Generates | Blockifies to | Inlinifies to | | - | - | - | - | - | | `inline flow-loose` | `inline` | inline box | block-level block container | inline box | | `inline flow-tight` | | inline-level block container (with BFC) | block-level block container | inline-level block container (with BFC) | | `inline flow-root` | | inline-level block container (with BFC) | block-level block container with BFC | inline-level block container (with BFC) | | `block flow-loose` | | block-level block container | block-level block container | inline box | | `block flow-tight` | `block` | block-level block container | block-level block container | inline-level block container (with BFC) | | `block flow-root` | `flow-root` | block-level block container with BFC | block-level block container with BFC | inline-level block container (with BFC) | Not bad. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1496#issuecomment-305918339 using your GitHub account
Received on Friday, 2 June 2017 21:55:18 UTC