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

That's correct, they are different computed values in Blink, but I don't think that's observable other than in `::marker`, since `content: inherit` doesn't work, and `getComputedStyle` lies.

Regarding WebKit, note that `::marker` doesn't obey `content` at all. But anyways, `normal` and `none` are also different computed values,  since `none` sets the `hasEffectiveContentNone()` flag. Like in Blink, `content: inherit` doesn't work. But WebKit has something interesting: `getComputedStyle` doesn't lie, i.e. it can be `normal` or `none`, whatever you specified. The only exception is that `content: normal` resolves to `none` on `::before` and `::after`.

So this seems to imply that it's web compatible if elements keep `content: none` as-is in `getComputedStyle`. Though it was a [recent change](https://bugs.webkit.org/show_bug.cgi?id=235222), so maybe there hasn't been enough time to encounter compat problems.

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


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

Received on Wednesday, 30 March 2022 00:07:46 UTC