- From: jfkthame via GitHub <noreply@w3.org>
- Date: Wed, 13 May 2026 08:50:47 +0000
- To: public-css-archive@w3.org
The proposed resolution seems fine, as far as it goes; but I wonder if we should also clarify what [the spec](https://drafts.csswg.org/css-fonts/#valdef-font-style-oblique-angle--90deg-90deg) means when it says "The lack of an [`<angle>`](https://drafts.csswg.org/css-values-4/#angle-value) represents 14deg." Currently, Gecko handles this "lack of an angle represent[ing] 14deg" at [parse time](https://searchfox.org/firefox-main/rev/22adc0417a3dbf478c7af00d45daa311e2efdf8b/servo/components/style/values/specified/font.rs#304-309), so that `oblique` and `oblique 14deg` are internally the exact same value. The intended outcome of the discussion here, AIUI, is effectively saying that "represents 14deg" applies only at _used value_ time; _specified_ and _computed_ values both maintain the distinction between the absence of an angle and the presence of `14deg`. So I think it would be helpful to rephrase the "represents 14deg" sentence to make it more explicit that this is referring _only_ to the used value. (I'm aware we'll need to update Gecko's style code to handle this; that's fine, I'm not opposed to making such a change.) -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8291#issuecomment-4439083779 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 May 2026 08:50:51 UTC