- From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Mar 2017 17:28:55 +0000
- To: public-css-archive@w3.org
> If emoji is specified, or if auto is specified and the character is an emoji character, the browser searches the font stack specifically for a full-color character Right now, browsers don't have agreement about how exactly variation selectors interact with font selection (See https://github.com/w3c/csswg-drafts/issues/854). Apple platforms have particular behavior which it would be valuable to emulate in Apple browsers. I don't know about other platforms' / browsers' algorithms. Until that issue has an agreement on how variation selectors work, we shouldn't specify exactly how this property, and therefore variation selectors, work. > If there are Unicode variation selector characters in the text, should they over-ride the emoji/text values, or vice versa? CSS operates on elements, which hold sequences of code points in them. Variation selector code points modify a specific code point in the sequence. Because variation selectors are specific to a particular code point inside the text node, variation selectors should have a higher precedence than the CSS applied on the entire element. The CSS property should set a default which individual characters can opt-out of. (The only alternative would be for the web author to have to create <spans> around individual character clusters just to set the presentation style, which no author wants to do) -- GitHub Notification of comment by litherum Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/352#issuecomment-285108637 using your GitHub account
Received on Wednesday, 8 March 2017 17:29:04 UTC