Re: [csswg-drafts] [css-text][css-fonts] Override (Emoji) Variation Selectors

> I agree, though, that it's rather unlikely to encounter VS-15 in the wild

That's the sticker here.  The only point of an override option is to override usage of the VS-15/16 selector; as far as we can tell, approximately nobody is using those.

Any pointer to some application currently wanting all their emoji in one form vs another is, currently, just an argument that this property is wanted in its current form, where it can switch the emoji into one form vs the other.  It's not immediately obvious whether any particular usage would want to *specifically* override the variation selector if it was specified; many might very well be fine with honoring them.  

And even if they'd want to, the question is still how necessary/common it is, vs just letting the display occasionally be weird, or requiring the author to clean the data they're displaying to remove the variation selectors.  We don't provide all possible text-transforms, after all, just a handful that seem sufficiently  useful to justify speccing, implementing, and testing.  Currently we don't think overriding variation selectors qualifies here; we're open to changing our mind if/when authors start actually experiencing variation selectors in user-entered content and complaining about it.

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1144#issuecomment-323199374 using your GitHub account

Received on Thursday, 17 August 2017 21:28:38 UTC