Intent to Implement: Render Unicode control characters

[Emil A Eklund]

Contact emails
e...@chromium.org

Spec
https://drafts.csswg.org/css-text/#white-space-fprocessing

Summary
Currently Chrome and other browsers do not render unicode control
characters. This violates the unicode spec and the handling in other
software. With this change non-white-space control characters will be
rendered.

Motivation
A few months ago, the CSSWG realized that all the browsers were
violating Unicode, by not rendering non-WS control characters
<https://lists.w3.org/Archives/Public/www-style/2014Mar/0475.html>.

It was decided that it made sense to match Unicode (and, likely,
other software) and display them instead. As such the spec has been
updated to address this.

Compatibility Risk
In order to minimize the impact of the change for web developers the
major browser vendors have all agreed to flip the switch around the same
time frame. We're targeting Chrome 47 which fits the agreed "around
November" timeline.

Ongoing technical constraints
None

Will this feature be supported on all six Blink platforms (Windows,
Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes

OWP launch tracking bug
crbug.com/530348

Link to entry on the feature dashboard
https://www.chromestatus.com/features/6232200047493120

Requesting approval to ship?
Yes

[Tab Atkins Jr.]

LGTM

> To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.