- From: 一丝 via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Oct 2024 15:57:31 +0000
- To: public-css-archive@w3.org
@jfkthame > It seems to me that if the author wants an emoji-style up-arrow here, but does not want the rendering of the following digits to be affected, the right approach would be to encode the arrow as <U+2B06, U+FE0F>. That's how you control the presentation of a specific character. Often the text entered is not under the control of the CSS author, such as when it is entered by a third party user from a CMS. We can't expect third-party users to learn how to enter a `Variation Selector`, or even just copy and paste an emoji character from somewhere else. That's why CSS authors need to change it to emoji style with `font-variant-emoji: emoji`, which I believe is one of the most common scenarios where this property is used. > Applying `font-variant-emoji` to a wider range of text inherently risks affecting other characters besides the intended one. The purpose of this issue is to minimize such risks, and digits are the most obvious ones. CSS should not give authors unexpected negative surprises. -- GitHub Notification of comment by yisibl Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11014#issuecomment-2432716808 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 October 2024 15:57:32 UTC