- From: Mike Bremford via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Sep 2021 15:57:01 +0000
- To: public-css-archive@w3.org
`font-palette: none` came from my feedback after we implemented. We didn't test with a huge number of emoji fonts, but at least Segoe UI (which uses COLR) has useful monochrome outlines in `glyf` as well as well as COLR: here's U+23F0 using both:  `font-variant-emoji` won't help us select them; prefixing U+23F0 with U+FE0E (what we'd get if `font-variant-emoji: text` were implemented) has no effect, this isn't a sequence in the fonts GSUB table. Obviously one glyph from one font is not be representative, but where SVG fonts are not supported Segoe UI is a likely choice for emoji. It contains useful monochrome outlines; we have a use-case where we need monochrome output; there's no existing mechanism to select them where they exist. `font-palette:none` seemed a reasonable approach. But I appreciate the world is moving towards SVG fonts; agreed they are far less likely to have a glyf outline, there are some monochrome options available, and we now support them so our need to do this with COLOR fonts is reduced. Ultimately if it can't be implemented by anyone other than us there's no point having it in the standard, so if it's causing a problem we're fine with dropping it. -- GitHub Notification of comment by faceless2 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6622#issuecomment-923057955 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 September 2021 15:57:03 UTC