[csswg-drafts] [css-fonts] Clarification font-variant-emoji should not affect characters `0-9#*` (#11014)

yisibl has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-fonts] Clarification font-variant-emoji should not affect characters `0-9#*` ==
> 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. Within this CSS specification, these characters are referred to as Emoji Presentation Participating Code Points. This property has no effect on any other characters.

Consider the following use case:

```html
data:text/html;charset=UTF-8,<!doctype html>
<style>
  .test { font-size: 52px; }
  .test { font-variant-emoji: text; font-family: system-ui, sans-serif; }
</style> 

<div class="test">⬆379 kB/s</div>
```

![image](https://github.com/user-attachments/assets/64fd0c29-d1b9-4ea1-8d5c-d736d4adc291)


The author only wants to change the style of the arrow (⬆︎), but when font-variant-emoji: emoji is applied, the font-family of the number `379` also becomes the font-family of the Emoji. this is something the author doesn't want.

Although, [UTS#51](https://www.unicode.org/reports/tr51/#Identification) states that `0-9#*` [have the `Emoji` property,](https://www.unicode.org/Public/16.0.0/ucd/emoji/emoji-data.txt#:~:text=E0.0%20%20%20%5B1%5D%20(*%EF%B8%8F)%20%20%20%20%20%20%20asterisk-,0030..0039,-%3B%20Emoji%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%23%20E0.0%20%20%5B10) I think they should be excluded from font-variant-emoji.

```
emoji_character := \p{Emoji}
https://www.unicode.org/reports/tr51/#def_emoji_character
```

Since Chrome has shipped, we need to clarify this in the CSS specification as soon as possible.

I've already filed a bug for Chrome: https://issues.chromium.org/issues/369781730

cc @svgeesus @drott @jfkthame @markusicu 

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11014 using your GitHub account


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

Received on Wednesday, 9 October 2024 13:55:15 UTC