- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Oct 2021 16:12:17 +0000
- To: public-css-archive@w3.org
Hyphenated prefixes seem more problematic to me, because (especially if we may eventually have quite a lot of them) they potentially conflict with author-specified font family names. It's not too much of a stretch to imagine an author writing `@font-face` rules to define a family such as `latin-cursive` or `euro-modern`, etc., never expecting it to clash with built-in generics. I'm not sure `generic(....)` is really a problem. If it causes old browsers to drop the entire declaration as invalid, authors should simply provide two `font-family` declarations: first, one for old browsers using only the existing syntax, and then override it with a new-syntax version for browsers that understand it. -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6770#issuecomment-953994583 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 October 2021 16:12:19 UTC