[css-display] Use "computes to" instead of "behaves as" for display: contents on unusual elements. #2755
Which means that the computed value of
In particular, it requires a mapping from element to "is really display contents", or something of the sort. Firefox used to have that, but it caused a lot of performance issues for no gain, so I removed it in https://bugzilla.mozilla.org/show_bug.cgi?id=1303605.
(Note that I removed that mapping earlier without realizing the correctness issue it introduced, https://bugzilla.mozilla.org/show_bug.cgi?id=1453702, which I fixed computing to none instead of contents, which also aligns with Blink and WebKit).
The text was updated successfully, but these errors were encountered:
The Working Group just discussed
The full IRC log of that discussion<dael> Topic: Use "computes to" instead of "behaves as" for display: contents on unusual elements
<dael> github: https://github.com//issues/2755
<dael> fantasai: We had said that display contents behaves as display:none on certain elements like some SVG. There's an appendix of exactly which ones. emilio filed an issue to jsut say computes to display:none since that's easier from impl then handling that at used style time
<dael> fantasai: TabAtkins and I have not much of an opinion. Up to impl.
<dael> emilio: Do we clear everyone that impl computes to none?
<fantasai> s/Do we/To be/
<astearns> s/Do we/To be/
<dael> Rossen_: Any reason to do anything other than that? Sounds like there's interop.
<dael> Rossen_: Objections to serialize it out as none?
<dael> RESOLVED: serialize it out as none
<dael> RESOLVED: compute to none
…ed elements. #2755 per WG resolution