W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2017

[csswg-drafts] [css-text] Control characters

From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
Date: Wed, 15 Nov 2017 19:04:15 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-274268732-1510772653-sysbot+gh@w3.org>
upsuper has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-text] Control characters ==
There was a long thread in www-style discussing about how control characters should be rendered, and that resulted in the following text in css-text-3:
> Control characters (Unicode category Cc) other than tab (U+0009), line feed (U+000A), form feed (U+000C), and carriage return (U+000D) must be rendered as a visible glyph and otherwise treated as any other character of the Other Symbols (So) general category and Common script. 

It seems to me that no browser is currently shipping this behavior, and IIRC we wanted to coordinate shipping this behavior together so that websites know it is an intentional behavior change for the platform.

I'd like to ask are we still want to do so? Firefox has implemented a switch for the new behavior since long ago, and we have it enabled by default for Nightly and early Beta. We are able to ship this change at any time, but we don't want to ship it without intent from other vendors. (And although it is not a big deal, the switch itself still adds some burden to maintaining, especially given that this switch wasn't supposed to stay for long.)

@gregwhitworth, @tabatkins, @litherum have Edge / Blink / WebKit implemented this switch? Can we start coordinating shipping the new behavior again?

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1990 using your GitHub account
Received on Wednesday, 15 November 2017 19:04:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 15 November 2017 19:04:19 UTC