W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2018

Re: [csswg-drafts] [css-fonts-4] font-variant-emoji: Consider broadening to all "color fonts" use-cases, not just emoji PPCP

From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
Date: Wed, 28 Feb 2018 06:49:54 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-369139091-1519800593-sysbot+gh@w3.org>
I don't think you've motivated the reason for this change. You said

> the implementators already have to do just as much work to implement the draft property

but saying it's easy to implement is not sufficient to add a new feature to the Web platform.

As I understand it, the request is to open this property up to color fonts, not just emoji. However, the problem we're dealing with really is emoji-specific. There are two situations where color fonts (not emoji) may be used:

- If the content author specifies a color web font in their `font-family` list
- If the browser falls off the end of the `font-family` list and needs to pick something from the set of installed fonts

If the content author doesn't want color fonts in the first case, they should just remove the item from the font-family list. The second case will never occur because no OSes (that I know of) come installed with color fonts. Therefore, this problem is only about the style of emoji.

Or, stated differently: I haven't ever heard content authors complaining about how a color font is being used accidentally. On the other hand, I have heard content authors complaining about how their [unicode snowmen](http://unicodesnowmanforyou.com) don't look like emoji.

Lastly, the existing property has specific semantics around treating text as if it has variation selectors. However, the Web platform does not have interop regarding variation selector behavior. It's under-specified, and it's conceivable (desirable?) that the behavior may change or be standardized in the future. If CSS uses the same signal for both variation selectors and color fonts, we lose the freedom to create standard compatibility for the behavior of variation selectors in the future.

GitHub Notification of comment by litherum
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2304#issuecomment-369139091 using your GitHub account
Received on Wednesday, 28 February 2018 06:49:56 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:24 UTC