Join GitHub today
[css-display] Should 'run-in flow-root' blockify to 'block' or 'flow-root'? #1715
I was drawing a diagram to understand the CSS Display transformations after the F2F resolutions and how a hypothetical
I noticed that it's not clear how
It was resolved that
The other possibility would be to keep it simple and only change the outer display type, i.e. blockify to
In practice, the difference should not matter much because I expect blockifications to trigger becoming a formatting context. But it will affect
I don't have a strong opinion, but maybe I prefer consistency with
The Working Group just discussed
The full IRC log of that discussion<dael_> Topic: Blockifying 'run-in flow-root' to 'block' (for consistency with inline-block)
<dael_> github: https://github.com//issues/1715
<dael_> florian: Was an alternative considered? I can't think of one.
<dael_> TabAtkins: It's the question in the title. Should it blockify to flow-root. It shouldn't.
<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.
<dael_> TabAtkins: Alternative is if blockifies to flow-root which makes sense in abstract, but we'd loose the connection to inline.
<dael_> florian: Consistancy argument wins or theoretical purity
<dael_> astearns: Run in flow root blockifies to block and not flow root
<dael_> astearns: Obj?
<dael_> RESOLVED: Run-in flow-root blockifies to block and not flow root