- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Apr 2020 03:48:10 +0000
- To: public-css-archive@w3.org
One thing I don't see mentioned here is that every new generic font keyword is a breaking change. Font family names have never needed to be quoted, which means the parser doesn't have any way to distinguish a generic keyword from a family name. Per the [font matching algorithm is currently defined](https://drafts.csswg.org/css-fonts/#font-style-matching), `font-family: script;` will look for: - first, an `@font-face` rule with a `font-family: blackletter` descriptor - failing that, a font named “blackletter” installed on my computer. If we add a `blackletter` generic, both of those would be overridden by the new generic mapping. Now, most systems won't have installed fonts that match a simple keyword name, but some internal / controlled systems will. And it is much more common to use simple keywords to describe your own web fonts. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4910#issuecomment-620974637 using your GitHub account
Received on Wednesday, 29 April 2020 03:48:11 UTC