Re: [csswg-drafts] [css-content] Implementing content:none on elements is not web-compatible (#6503)

> Though `none` still behaves as `normal` in many situations; i.e. the used value of `none` may still be `normal`.

This is the important point here. For elements, the used value needs to be `normal`. The examples of broken pages linked to from the [Mozilla bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1719239) all had in common that they accidentally hide normal elements with `content: none` while they only wanted to empty the pseudo-elements `::before` and `::after` or not empty the content at all.

Sebastian

Sebastian

-- 
GitHub Notification of comment by SebastianZ
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6503#issuecomment-1091614206 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 7 April 2022 11:21:29 UTC