A similar issue in CSS Color was dealt with by making the author-supplied identifiers be dashed idents. I don't thinks we can do that here though, because the weight of existing usage is too great. So yes, if we constantly make new generics then there is a risk that they clash with previously-ok user supplied names. The only wiggle room we have is the use of quoting: ```css @font-face { font-family: "serif"; ...} html { font-family: "serif", serif } ``` This will use the webfont called "serif" and then as fallback the generic font family `serif`. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5001#issuecomment-728942065 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Tuesday, 17 November 2020 13:53:15 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:22 UTC