- From: DeeDeeG via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Feb 2018 19:35:50 +0000
- To: public-css-archive@w3.org
P.S. The draft property discussed in #1092 is about already font selection. (Unless I am mistaken.) So I didn't mean to deviate far from that starting point. The reason why I think my suggestion here would be a good idea, is that I think the implementators already have to do just as much work to implement the draft property discussed in #1092 (but implementors of that draft property must limit the property's behavior to affect only emoji PPCP codepoints). The only difference is, given my suggestion is added to the spec, authors can use that color font selection behavior on arbitrary text (arbitrary codepoints), not just emoji PPCP codepoints. It expands the font selection toggle to all text / all codepoints. Outside of emoji PPCP codepoints, this would allow a more generic `font-family` value to be assigned to lots of elements, but some elements designated as `rich` and other elements designated as `traditional`, so as to select an explicit-color or else traditional font. It's a higher-level, more abstracted way of selecting explicit-color vs traditional fonts, compared to simply ensuring the correct font is toward the from in `font-family` value for a given element. (And it is just as capable of sorting out emoji PCCP issues as is the draft discussed in #1092). -- GitHub Notification of comment by DeeDeeG Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2304#issuecomment-367444470 using your GitHub account
Received on Wednesday, 21 February 2018 19:36:05 UTC