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

> WebKit (and other browsers too?) will consider this kind of signal when we "fall off the end" of the font-family list and have to pick a font for the content but can't use any of the fonts in the specified list.

Can you elaborate on this? I don't understand what you mean - are you saying that if the author puts `serif` at the end of their stack, but they use a character not mapped by the font that WebKit assigns to `serif`, it'll still influence what *additional* fonts WebKit looks for to find a mapping for the character?

GitHub Notification of comment by tabatkins
Please view or discuss this issue at using your GitHub account

Received on Monday, 28 October 2019 22:00:40 UTC