- From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 May 2018 04:57:42 +0000
- To: public-css-archive@w3.org
upsuper has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-content] Description about <content-replacement> doesn't match what implementations do for pseudo-elements == The spec currently says that [`<content-replacement>` value](https://drafts.csswg.org/css-content-3/#typedef-content-content-replacement) should: > Makes the element or pseudo-element a replaced element, filled with the specified `<image>`. Its normal contents are suppressed and do not generate boxes, as if they were `display: none`. And there is a note in [`<content-list>` value](https://drafts.csswg.org/css-content-3/#typedef-content-content-list) mentioning: > If the value of <content-list> is a single <image>, it must instead be interpreted as a <content-replacement>. This doesn't match what `content` with a single url means in [CSS 2](https://www.w3.org/TR/CSS22/generate.html#propdef-content), nor how it is implemented in browsers. Given #2656, I would suggest that we make the single url mean `<content-list>` for pseudo-element, and `<content-replacement>` is only for elements. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2657 using your GitHub account
Received on Tuesday, 8 May 2018 04:57:50 UTC