Re: [csswg-drafts] [css-fonts-4] @font-face unicode-range and first available font

I think Gecko's behavior here is that, the first available font which has `unicode-range` covers whitespace is used. That says, in the test case provided above, we should match behavior of Blink and WebKit, but if a local font (not defined by @font-face rule) is checked, it will be used unconditionally (because it doesn't have `unicode-range` specified). I'm not sure whether this could be a problem, or does it match other browsers' behavior.

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

Received on Sunday, 10 September 2017 23:26:35 UTC