- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Sep 2023 07:41:43 +0000
- To: public-css-archive@w3.org
> About `<family-name>#` in the prelude of `@font-feature-values`: > > > [...] rules that include generic or **system fonts** in the list of font families are syntax errors I suspect *system fonts* should have been replaced by *installed fonts* in https://github.com/w3c/csswg-drafts/commit/e208889cefc2aafbf7b0a007c69c3471a1b387cf, and it should even be entirely removed like in https://github.com/w3c/csswg-drafts/commit/3d1ac3cfd08e8b3a0e2033f1846c8b463999fd77. But then I wonder if a system font name should be parsed as a valid `<family-name>` in: - `font-family` for `@font-face`: there is currently no restriction - `font-family` for `@font-palette-values`: generic fonts are currently syntax errors - the prelude of `@font-feature-values`: generic fonts (at least) are currently syntax errors I think `<family-name>` generally excludes generic font names and system font names, but only in `font-family` for a style rule: > Any identifier which could be misinterpreted as a pre-defined keyword in the `font-family` value definition, or the CSS-wide keywords, is not allowed. https://drafts.csswg.org/css-fonts-4/#family-name-syntax I suspect it should exclude all pre-defined keywords, regardless of the context in which it appears. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9292#issuecomment-1706104348 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 5 September 2023 07:41:46 UTC