W3C home > Mailing lists > Public > public-css-archive@w3.org > December 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: Tue, 03 Dec 2019 20:25:37 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-561341977-1575404735-sysbot+gh@w3.org>
The difference is that @frivoal says

> falling through a generic font family to whatever is after it, be it another generic, or a "real" font family

so Helvetica would be used

while I am thinking that if serif fails, we are on to [step 3 listed above](https://github.com/w3c/csswg-drafts/issues/4442#issuecomment-551170705)

so the implementation-specific, wide-coverage fallback font would be used.


-- 
GitHub Notification of comment by svgeesus
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4442#issuecomment-561341977 using your GitHub account
Received on Tuesday, 3 December 2019 20:25:39 UTC

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