- From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Sep 2021 19:01:34 +0000
- To: public-css-archive@w3.org
litherum has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-fonts] Remove the none value from font-palette == There are a few reasons to remove it: 1. It's unimplementable on Core Text. 2. It [was added](https://github.com/w3c/csswg-drafts/issues/4699) without WG input. 3. Clearly the font creator wants their clients to use the font's color facilities; otherwise they would not have created them. 4. One of the motivations for adding it is false: "Both SVG and COLR fonts must have a regular, uncolored glyph outline available." This is untrue - the fallback might have 0 contours. Many (perhaps even "most"!) of the color fonts we've seen have no outline fallback. 5. Another motivation was misplaced: "Many glyphs in the "emoji" range will only exist in a font with color capabilities" We already have two mechanisms for selecting non-color emoji: both variation selectors and https://drafts.csswg.org/css-fonts/#font-variant-emoji-prop. Text-style emoji is handled with font fallback, not displaying otherwise-unobservable contours inside fonts. 6. If the page author wants a non-color rendering, they can use a non-color font. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6622 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 16 September 2021 19:01:36 UTC