- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Jan 2025 16:23:09 +0000
- To: public-css-archive@w3.org
[According to the spec](https://drafts.csswg.org/css-fonts-4/#valdef-font-style-normal), `normal` is essentially a convenience value that means the same as `oblique 0deg`: > This represents an oblique value of "0". So surely they should serialize the same. The shortest-form principle (as well as backwards-compat concerns) dictates that this should be `normal`. And AFAICS that's what shipping versions of all the engines currently do. Is there a compelling reason to change this behavior? If it's just that the spec is a bit confusing (hence this discussion!), I suggest we add a note clarifying that `oblique 0deg` always computes to `normal` (including during animation; the remark that "normal animates as oblique 0deg" refers to how this value is interpolated with other oblique values, it does not alter how it serializes). -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11430#issuecomment-2569492707 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 3 January 2025 16:23:10 UTC