- From: Guillaume via GitHub <noreply@w3.org>
- Date: Sun, 28 Dec 2025 13:30:39 +0000
- To: public-css-archive@w3.org
So to continue/answer my previous comment, `<generic-family>` and `<system-family-name>` are both excluded from *the set of all font families* because they are valid only in specific contexts: - `font` for `<system-family-name>` - `font-family` for `<generic-family>` `<family-name>` is the only production used in different contexts: `@font-face/font-family`, `@font-face/font-src`, `@font-feature-values`, `@font-palette-values`. As defined in the spec, a generic font family *keyword* is an alias for one or more font family names, which appears to be the only reason for the *family **name*** redudancy. In my opinion, the use of *generic font family name* seems confusing. Referring to font family names and keywords as *font families* does not seem perfect, but it seems acceptable. So my first thought was that, ideally, `font-family` should be defined with `[<custom-ident> | <string> | <generic-font-family>]#`, and that `<'font-family'>` should be used to define `@font-face/font-family`, `@font-face/src`, `@font-feature-values`, by excluding `<generic-font-family>` and `<system-font-family>` in prose when appropriate, which might not be ideal. So then I thought `<user-font-family>`, `<generic-font-family>`, `<system-font-family>`, could make sense. But that was not the original purpose of this issue, which was to remove the ambiguity between voice and font families. I will therefore leave this suggestion to another issue, if it proves appropriate. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13263#issuecomment-3694749054 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 28 December 2025 13:30:39 UTC