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

I'm for overrides. Authors should be able to style text the way they want. 

For example, I might be designing a social media oriented site, with an expectation of showing emoji, but users might copy/paste and submit text that includes vs-15 unwittingly. Most users do not know about or understand how to type/delete variation selectors, so this could cause a problem where users complain they aren't seeing emoji when they should be.

Or, I could be designing a site (or a blog theme, to be redistributed freely) where headers should always display emoji, as a deliberate style choice, regardless of whether a vs-15 was accidentally included.

On the contrary, as Crissov linked to, some folks really do need to be able to style things as text, to make sure they have the expected visual, and to aid accessibility by ensuring high contrast, or even just to be consistent with surrounding text.

And typing/deleting variation selectors is cumbersome. Many I would presume don't know how. A css style should be able to force consistency.

(On the other hand, once these proposed CSS controls are implemented, and VS-16/VS-16 behavior is properly standardized, it might be more obvious that the VS characters need to be entered correctly, and the impetus could be on the person who provides the text to make sure they are providing the correct presentation (i.e. Typing correctly, or else copying/pasting from the right source))

(Deleted my comments from before, as they were based on a misunderstanding.)

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

Received on Sunday, 16 April 2017 19:32:18 UTC