Skip to content

Conversation

@alisonmaher
Copy link
Collaborator

The team in Chromium making the updates to forced colors mode emoji handling noted that it would be helpful to specify that font-variant-emoji gets overridden to text to ensure that the monochrome variant is chosen if available. This change adds more text to specify the exact details.

I wasn't sure if a new resolution was needed for this given the resolution in #8064 (comment) but more than happy to file a new issue as needed.

Copy link
Collaborator

@fantasai fantasai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like an editorial clarification.

Does bring up a few questions though:

  • Should this be a used-value change or a computed-value change?
  • What happens if an emoji has a variation selector that indicates color emoji? If I'm reading the spec correctly here https://www.w3.org/TR/css-fonts-4/#propdef-font-variant-emoji font-variant-emoji doesn't have an effect in this case...? But it's a bit unclear from the spec. CC @svgeesus

@alisonmaher
Copy link
Collaborator Author

Should this be a used-value change or a computed-value change?

@fantasai this is a good question and one that I was going back and forth on. I chose used value time since we check against the computed value of font-variant-emoji before overriding, but that can also be done at computed value time.

And I suppose computed value time is more consistent with all of the other non-color based properties, so perhaps that is a better choice. If others agree, I can make that update

@svgeesus
Copy link
Contributor

svgeesus commented Oct 3, 2025

I believe that is correct, but may take a closer reading of the spec and perhaps making assumptions about what "appended" means exactly in code point order. My reading is that the "as if appended" puts it last, thus over-riding any actual VS in the text.

Suggestions for simpler but clearer wording welcome, of course (but need not hold up merging this PR).

And I suppose computed value time is more consistent with all of the other non-color based properties, so perhaps that is a better choice. If others agree, I can make that update

I think it is a more consistent choice, yes.

@alisonmaher
Copy link
Collaborator Author

And I suppose computed value time is more consistent with all of the other non-color based properties, so perhaps that is a better choice. If others agree, I can make that update

I think it is a more consistent choice, yes.

Sounds good, updated to computed value time for consistency

@alisonmaher alisonmaher merged commit cddf38c into w3c:main Oct 3, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants