- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Jan 2018 15:51:55 +0000
- To: public-css-archive@w3.org
Reopening for discussion. I suggest to mark this as fixed, for the following reasons: If I am not mistaken in my interpretation of the spec, I found that not doing system fallback for PUA is in fact already spec'ed (thanks to Kunihiko Sakamato for pointing this out in [Chromium issue 803305](https://bugs.chromium.org/p/chromium/issues/detail?id=803305#c8) https://drafts.csswg.org/css-fonts/#char-handling-issues > If a given character is a Private-Use Area Unicode codepoint, user agents must only match font families named in the ‘font-family’ list that are not generic families. If none of the families named in the ‘font-family’ list contain a glyph for that codepoint, user agents must display some form of missing glyph symbol for that character rather than attempting system font fallback for that codepoint. It's been there for 2years+: https://github.com/w3c/csswg-drafts/blob/master/css-fonts-3/Fonts.src.html#L2667 -- GitHub Notification of comment by drott Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2110#issuecomment-361289144 using your GitHub account
Received on Monday, 29 January 2018 15:51:59 UTC