- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Jan 2024 15:12:24 +0000
- To: public-css-archive@w3.org
Since this issue was last discussed, CSS Fonts 4 [introduced three categories](https://drafts.csswg.org/css-fonts/#font-prop):
1. **Set Explicitly**
These properties may be set using the [font](https://drafts.csswg.org/css-fonts/#propdef-font) property
2. **Reset Implicitly**
These may not be set, but are reset to their initial values
3. **Cascaded Independently**
There are neither set nor reset by the [font](https://drafts.csswg.org/css-fonts/#propdef-font) property
And [font-palette](https://drafts.csswg.org/css-fonts/#propdef-font-palette) is in the third category; neither set nor resent by the `font` shorthand.
> E.g. in the WPT test [font-palette-vs-shorthand](https://github.com/web-platform-tests/wpt/blob/master/css/css-fonts/font-palette-vs-shorthand.html) it is unclear if the elements with the following styles:
> `#a { font: 50px colr; font-palette: dark; }` and
> `#c { font-palette: dark; font-size: 50px; font-family: colr; }` should reset `font` shorthand property to "". Chrome currently doesn't do that but Firefox does.
If Firefox till does, that is contrary to the spec. [The test](https://github.com/web-platform-tests/wpt/blob/master/css/css-fonts/font-palette-vs-shorthand.html) seems to me to be correct.
My conclusion is that the spec is self-consistent and WPT reflects the spec correctly on this point.
--
GitHub Notification of comment by svgeesus
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8062#issuecomment-1906257627 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 January 2024 15:12:27 UTC