- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Sep 2023 04:37:58 +0000
- To: public-css-archive@w3.org
Before the changes fixing this issue, `<generic-family>` was (and is still) defined as a keyword. > **`<generic-family>`**: Each `<generic-family>` keyword represents a generic font choice [...] Now it is not clear: > `<generic-family> = generic( <custom-ident>+ ) | <string> | <custom-ident>+` Is it intentional to allow `<string>` and one *or more* custom identifiers? I would prefer to have generic font family names inlined in the value definition or abstracted with `<generic-family-name>` (for example) rather than `<custom-ident>`. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6770#issuecomment-1724819811 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 September 2023 04:37:59 UTC