| Summary: | ER: Ignore vendor names in font family lookup | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Nicholas Shanks <nickshanks> |
| Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Enhancement | CC: | ian, mmaxfield |
| Priority: | P5 | ||
| Version: | Safari 14 | ||
| Hardware: | Mac | ||
| OS: | All | ||
| See Also: | https://github.com/w3c/csswg-drafts/issues/5819 | ||
Mitz says this makes sense. Filed https://github.com/w3c/csswg-drafts/issues/5819 to try and get some guidance as to whether this is even something we should be considering per-spec; bumping priority down to P5 given this clearly isn't a priority. |
Say a website specifies the following CSS: h1 { font-family: "Century", "Garamond", serif; } And the user has the following fonts installed: Apple Garamond BT Adobe Garamond New Century Schoolbook The initial search for a font matching "Century" will fail, as it ought to. However so will the search for Garamond. I believe instead one of the two Garamonds installed should be matched. This can be achieved by having a second font list stripped of all vendor names, which would be searched after exhausting all named families, before resorting to the generic "serif". Likewise, the common terms "Std" and "Pro" could be removed, allowing "Stone Serif" to match "ITC Stone Serif Pro" for example.