- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Nov 2024 09:18:02 +0000
- To: public-css-archive@w3.org
> Why not use the unicode keyword? > Because it doesn't allow common emoji like ⬆︎, ❤︎ to be in color style. It does, with VS16. > If I understand correctly, `RGI_Emoji_Qualification` in UTS 51 seems to be a solid solution, where `0-9*#` is not included. `RGI_Emoji_Qualification` is not suitable, because * it is not a character property, but an enumeration of strings. (we need the former in emoji segmentation) * is too restrictive, as it enumerates the RGI Emoji set - which is different from what can occur in fonts and as you point out, [misses certain used sequences](https://github.com/mathiasbynens/emoji-test-regex-pattern/issues/7#issuecomment-2414525703). -- GitHub Notification of comment by drott Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11014#issuecomment-2505624177 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 November 2024 09:18:03 UTC