W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2019

[csswg-drafts] [css-content] content: contents will not be compatible. (#4632)

From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
Date: Thu, 26 Dec 2019 21:58:18 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-542679656-1577397497-sysbot+gh@w3.org>
emilio has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-content] content: contents will not be compatible. ==
I was fixing a Gecko compat issue (https://github.com/webcompat/web-bugs/issues/46914) which is present because we always serialize `content: normal` as `content: none`, even on elements.

I'm going to fix Gecko to follow the spec and `getComputedStyle()` returns `none` for pseudo-elements, but not for elements. But such code wouldn't work if we were to make `content: normal` compute to `content: contents` on elements either, which is what the latest draft specifies: https://drafts.csswg.org/css-content/#content-property

So I propose for `content: normal` to compute to itself for elements, and removing `content: contents` from the spec.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4632 using your GitHub account
Received on Thursday, 26 December 2019 21:58:20 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:57 UTC