- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Dec 2019 11:32:49 +0000
- To: public-css-archive@w3.org
Changing the computed value of `content: normal` seems bad.
If `content: normal` computes to `contents` in elements, it means that in
```css
#foo { content: normal }
#foo::before { content: inherit }
```
the `::before` will inherit `content: contents`. But in `::before`, `contents` has a very different meaning than `normal` (even if it will still behave as `none` because `contents` can only be used once per element).
I'm also not sure about computing `content: normal` to `none` in pseudo-elements. It implies that in
```css
#foo::before {
content: normal;
display: list-item;
}
#foo::before::marker {
content: inherit;
}
```
the `::before::marker` will inherit `content: none`, even if in markers `none` has a completely different meaning than `normal`. Probably not much important since the marker won't be displayed, but IMO seems strange.
So I support `content: normal` computing to `normal` in elements and staying as `normal` in `getComputedStyle` for compat. I also tend to think that `content: normal` should compute to `normal` in pseudo-elements, but probably have a resolved and used value of `none`.
--
GitHub Notification of comment by Loirooriol
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4632#issuecomment-569251633 using your GitHub account
Received on Friday, 27 December 2019 11:32:50 UTC