- From: J. S. Choi via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Mar 2018 20:33:12 +0000
- To: public-css-archive@w3.org
On the other hand, is there a reason why a `auto` option that would leave presentation to the browser/platform would be desirable? Is this something that vendors want? Inconsistencies with Unicode TR 51 have caused unexpected changes to previously authored content on the web. For instance, in 2015, WebKit unexpectedly started to render U+21A9 LEFTWARDS ARROW WITH HOOK “↩” as emoji rather than text in many pages that had been using it as text, even for decades. See [Daring Fireball note](https://daringfireball.net/linked/2015/04/22/unicode-emoji) and [Matias Singers post](http://mts.io/2015/04/21/unicode-symbol-render-text-emoji/). Had WebKit been following Unicode TR 51, this author-unexpected behavior would not have happened. Unicode provides a Unicode_Presentation property for a reason: to prevent author-unexpected cases just like this. -- GitHub Notification of comment by js-choi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1223#issuecomment-370918322 using your GitHub account
Received on Tuesday, 6 March 2018 20:33:16 UTC