- From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Dec 2021 00:39:04 +0000
- To: public-css-archive@w3.org
litherum has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-fonts-4] PUA fallback == The [spec](https://drafts.csswg.org/css-fonts-4/#char-handling-issues) currently says: > 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. This should probably be made more strict. Because PUA characters are font-specific, and websites don't know what fonts are installed on the system, no installed font should match any PUA characters. @svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6851 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 December 2021 00:39:06 UTC