- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Oct 2023 18:08:10 +0000
- To: public-css-archive@w3.org
So the question is, whether implementers are willing to deal with the overhead of a property alias and a descriptor alias to finally get rid of this wart? IF so, my proposal is: - A property `font-width` exists (with largely same description that `font-stretch` currently has). - For historical reasons, a property `font-stretch` exists which is an alias of `font-width` - Setting `font-width` also sets `font-stretch` to the same value - Setting `font-stretch` also sets `font-width` to the same value - Getting either property returns that one value. also - a descriptor `font-width` exists on `@font-face` (same spec text as current `font-stretch` descriptor) - for historical reasons, a descriptor `font-stretch` also exists which has the same meaning as `font-width` and is treated as being the same - as with [other `@font-face` descriptors](https://drafts.csswg.org/css-fonts-4/#font-face-rule) we use the "last one wins": > When a given descriptor occurs multiple times in a given `@font-face` rule, only the last descriptor declaration is used and all prior declarations for that descriptor are ignored. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/551#issuecomment-1755972551 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 October 2023 18:08:12 UTC