- From: Mats Palmgren <mats@mozilla.com>
- Date: Fri, 23 Dec 2016 21:13:25 +0100
- To: fantasai <fantasai.lists@inkedblade.net>, "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: www-style list <www-style@w3.org>, Jet Villegas <jet@mozilla.com>, "L. David Baron" <dbaron@dbaron.org>
On 12/23/2016 07:00 PM, fantasai wrote: > That said, I'd love to see you all at least *ask* us to officially > stabilize specs you're planning to ship before announcing that > you're going to do it anyway. Well, Tab said it was "stable design-wise" and then implied that he wanted to see someone shipping it: https://discourse.wicg.io/t/containing-floated-children-with-clear-after-modern-clearfix/1835/6 I took that as an OK to ship it; did I misunderstand? > In this case, I think we can easily transition a trimmed down version > of Display in January. It would help to know which of its features > Mozilla has or is planning to implement, and if there are any known > spec issues with those features. Only display:flow-root this time. We have previously shipped display:contents and the ruby values (and the obvious CSS2 values). We have *not* implemented 'run-in' yet though. We only support the single-keyword form of 'display'. AFAICT, the 'display' keywords we haven't implemented yet are: run-in, flow, inline-list-item Is the spec for these stable enough to implement and/or ship? I think we (Gecko) plan to implement 'inline-list-item'[1] at some point. I'm not aware of any plans to implement 'display:flow', but it seems kind of trivial (in its single-keyword form) so I don't see any reason not to. There's a (very old) bug filed on 'run-in' where someone said it was *removed* from Chrome/Safari[2] - was that because authors weren't very interested in this feature, or because of some other reason? Are they interested in adding it again? /Mats [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1105868 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=2056#c83
Received on Friday, 23 December 2016 20:13:56 UTC