Re: [csswg-drafts] [css-color-adjust-1] Emojis in forced colors mode (#8064)

The CSS Working Group just discussed `[css-color-adjust-1] Emojis in forced colors mode`, and agreed to the following:

* `RESOLVED: use monochrome emoji in forced-colors mode if the font-variant-emoji property is set to normal or unicode`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> alisonmaher:<br>
&lt;emeyer> alisonmaher: Today we aren't doing anything special<br>
&lt;emeyer> …Proposal is to call back to monochrome versions of emojis in forced-color mode<br>
&lt;emeyer> …Or else, no change to what happens now<br>
&lt;emilio> I think making font selection depend on forced-colors feels a bit too subtle<br>
&lt;emeyer> astearns: Any opinions?<br>
&lt;emilio> But also I don't think it matters much one way or the other<br>
&lt;emeyer> (silence)<br>
&lt;emeyer> ChrisL: Could you explain the interaction with variation selectors?<br>
&lt;emeyer> alisonmaher: I'm not familiar with that<br>
&lt;TabAtkins> q+<br>
&lt;astearns> ack emilio<br>
&lt;astearns> ack TabAtkins<br>
&lt;emeyer> TabAtkins: I think overall this looks reasonable<br>
&lt;emeyer> …The effect looks right<br>
&lt;emeyer> …Chris's point about grayscaling emoji is well taken but I don't think there's a good solution here<br>
&lt;emeyer> s/emoji/raster emoji/<br>
&lt;emilio> q+<br>
&lt;astearns> ack fantasai<br>
&lt;Zakim> fantasai, you wanted to ask if this should depend on font-variant-emoji<br>
&lt;emeyer> …We should maybe add a note about that case if we know what we want to say<br>
&lt;emeyer> fantasai: We have a font-variant-emoji proeprty, and I'm wondering if this should depend on that<br>
&lt;fantasai> normal | text | emoji | unicode<br>
&lt;emilio> q-<br>
&lt;emeyer> fantasai: Where normal means the user gets to choose and platform conventions are followed<br>
&lt;emeyer> …text means 15, emoji is 16, unicode is follow unicode's table<br>
&lt;emeyer> astearns: Are you suggesting we change to normal?<br>
&lt;emeyer> fantasai: Maybe to normal and unicode?<br>
&lt;emeyer> alisonmaher: That sounds reasonable to me<br>
&lt;dbaron> s/15/variation selector 15/<br>
&lt;emeyer> astearns: Does that answer your question, Chris?<br>
&lt;emeyer> ChrisL: Not sure, but it seems to say this would work with variation selectors unless you did a certain thing, and then it owuldn<br>
&lt;astearns> ack emilio<br>
&lt;emeyer> s/owuldn/wouldn't/<br>
&lt;emeyer> fantasai: The unicode value is the one that honors the variation selectors<br>
&lt;emeyer> …text ignores whatever's happening according to unicode rules and use text, and emoji also ignore the rules and use the color emoji<br>
&lt;emeyer> astearns: If I'm following, then are we coming to using monochrome emoji in forced-colors mode if the font-variant-emoji property is set to normal or unicode<br>
&lt;emeyer> fantasai: Alternative proposal is to use it for normal and unicode unless variation selector 16 is present, in which case allow that character to override and present in color<br>
&lt;emeyer> alisonmaher: Don't have a strong opinion here<br>
&lt;emeyer> fantasai: The advantage of the latter proposal is an author could pick out a specific character they want but I doubt people are doing that, so I lean tothe first option<br>
&lt;emeyer> s/tothe/to the/<br>
&lt;emeyer> ChrisL: Currently FF is the onlny browser to pass the relevent tests<br>
&lt;emeyer> astearns: But not Safari, which doesn't have forced-color modes, yes?<br>
&lt;ChrisL> I meant in general, the font-variant-emoji property<br>
&lt;emeyer> RESOLVED: use monochrome emoji in forced-colors mode if the font-variant-emoji property is set to normal or unicode<br>
&lt;ChrisL> https://wpt.fyi/results/css/css-fonts/parsing/font-variant-emoji-valid.html?label=experimental&amp;label=master&amp;aligned<br>
&lt;ChrisL> https://wpt.fyi/results/css/css-fonts/parsing/font-variant-emoji-computed.html?label=experimental&amp;label=master&amp;aligned<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8064#issuecomment-2163389692 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 12 June 2024 15:52:17 UTC