Re: [csswg-drafts] [css-fonts] Should font-variant-emoji affect ZWJ emoji sequences? (#11036)

> There are some ZWJ emoji sequences that do not have VS, compare https://www.unicode.org/Public/emoji/latest/emoji-zwj-sequences.txt. Should `font-variant-emoji` property affect any of the codepoints in these sequences?

Yes, in my opinion: the natural expectation would be that any character or sequence that displays an emoji-style glyph by default should change to a text-style glyph if `font-variant-emoji: text` is applied.

> Let's consider the following use case:
> 
> `<div style="font-variant-emoji: text">&#x1F408;&#x200D;&#x2B1B;</div>`
> 
> According to the [CSS Fonts Module 4 spec](https://www.w3.org/TR/css-fonts-4/#font-variant-emoji-prop):
> 
> > Only the code points [listed](http://www.unicode.org/emoji/charts/emoji-variants.html) by Unicode as contributing to a Unicode emoji presentation sequence are affected by this property.
> 
> U+1F408 is listed there, since U+1F408 U+FE0E is a valid variation sequence, compare: https://www.unicode.org/Public/15.1.0/ucd/emoji/emoji-variation-sequences.txt.
> 
> So the way I interpret spec right now, it example above should act as:
> 
> `<div">&#x1F408;&#xFE0E;&#x200D;&#x2B1B;</div>`
> 
> and split the zwj sequence.

The spec wording is perhaps unfortunate here, because I think users will assume that `font-variant-emoji` applies to "emoji text units", which may be individual codepoints *or* sequences; that distinction is not useful to users.

So in the case of `&#x1F408;&#x200D;&#x2B1B;`, applying `font-variant-emoji: text` does not insert an actual `U+FE0E` codepoint and break the sequence (resulting in a text-style cat, perhaps as a line-drawing or outline, followed by a black square); it's still an emoji sequence requesting a black cat, but now it's supposed to be a text-style black cat rather than an emoji-style one.


-- 
GitHub Notification of comment by jfkthame
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11036#issuecomment-2427101419 using your GitHub account


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

Received on Monday, 21 October 2024 16:03:36 UTC