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

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

From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
Date: Tue, 29 Oct 2019 18:55:47 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-547577857-1572375347-sysbot+gh@w3.org>
I assume that, in those questions, "fallback" means "the font that is used when the browser falls off the end of the `font-family` list".

In that case, I don't see any benefit to specifying how this font is picked. If the author wants the browser to pick a particular font, they should just name the font in the `font-family` list.

I do see benefit in leaving it unspecified because:

- We use platform (Core Text) APIs to do it, and these APIs were not created with the web, or any web concepts, in mind
- Browsers should be free to gather insight from any/all signals that the author has already provided in order to make the best pick possible.

GitHub Notification of comment by litherum
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4442#issuecomment-547577857 using your GitHub account
Received on Tuesday, 29 October 2019 18:55:49 UTC

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