W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2019

Re: [csswg-drafts] [css-fonts] Don't require browsers to always match every generic font family to a concrete font family (#4442)

From: Chris Lilley via GitHub <sysbot+gh@w3.org>
Date: Fri, 15 Nov 2019 01:02:06 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-554160606-1573779725-sysbot+gh@w3.org>
> Unless generic font families are required to produce some glyph for every code point (in other words option 2, which you're not advocating for), 


> then falling through a generic font family to whatever is after it,

which is step 3 in my mental model, listed above. If the generic (step 2) fails to produce a glyph, you are onto steps 3 and then 4.

GitHub Notification of comment by svgeesus
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4442#issuecomment-554160606 using your GitHub account
Received on Friday, 15 November 2019 01:02:13 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:56 UTC