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

Re: [csswg-drafts] [css-fonts] What does fangsong map to for non chinese text (#4425)

From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
Date: Fri, 18 Oct 2019 16:08:57 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-543813677-1571414937-sysbot+gh@w3.org>
> generic font families don't match a single font; they match a font stack

I can't speak for other browsers, but at least in WebKit, all of the generic font families except `system-ui` match only a single font, not an entire stack. I'm curious whether that's true in other browsers or not.

> the stack does cover as much of Unicode as the system can

The point I was trying to make is that there's no guarantee of how much of Unicode is actually covered.

Stated another way: The spec currently says:

> Each generic font family must always map to at least one matched font face.

If the goal here is to provide interoperability between browsers, then this statement doesn't actually provide any interoperability guarantees. I don't quite understand why this additional requirement is placed on implementations if it doesn't actually accomplish its goal.

I'm trying to argue that, instead of having some generic font families that always match something on the system and some that don't, we should just say that all of them don't.

But, I'm on a tangent. I should move this into another issue.

GitHub Notification of comment by litherum
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4425#issuecomment-543813677 using your GitHub account
Received on Friday, 18 October 2019 16:09:00 UTC

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