Re: [csswg-drafts] [css-display] Should 'run-in flow-root' blockify to 'block' or 'flow-root'?

The Working Group just discussed `Blockifying 'run-in flow-root' to 'block' (for consistency with inline-block)`, and agreed to the following resolutions:

* `RESOLVED: Run-in flow-root blockifies to block and not flow root`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael_> Topic:  Blockifying 'run-in flow-root' to 'block' (for consistency with inline-block)<br>
&lt;dael_> github:  https://github.com/w3c/csswg-drafts/issues/1715<br>
&lt;dael_> florian: Was an alternative considered? I can't think of one.<br>
&lt;dael_> TabAtkins: It's the question in the title. Should it blockify to flow-root. It shouldn't.<br>
&lt;dael_> TabAtkins: An inline flow root blockifies to an ordinary block. This is for legacy reasonings. A run-in flow-root needs to blockify somehow. The general rule for run-in they're identical to inlines. Thus it shoudl blockify the same as inlines.<br>
&lt;dael_> TabAtkins: Alternative is if blockifies to flow-root which makes sense in abstract, but we'd loose the connection to inline.<br>
&lt;dael_> florian: Consistancy argument wins or theoretical purity<br>
&lt;dael_> astearns: Run in flow root blockifies to block and not flow root<br>
&lt;dael_> astearns: Obj?<br>
&lt;dael_> RESOLVED: Run-in flow-root blockifies to block and not flow root<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1715#issuecomment-378776586 using your GitHub account

Received on Wednesday, 4 April 2018 23:29:38 UTC