Intent to Ship: Render Unicode control characters

[Emil A Eklund]

Contact emails
e...@chromium.org

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

Summary
In the past Chrome and other browsers did not render unicode control
characters. This violated the unicode spec and was inconsistent with
the handling in other software. With this change non-white-space control
characters will be rendered.

Motivation
Over a year 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. All other
browsers have now changed, we're the last hold out. It's been an
experimental web platform feature for months with no compat reports
and with this change we'll now, once again, match the other browsers.

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

[Philip Jägenstedt]

LGTM1

I found http://jsbin.com/wamerawapu/edit?output but can only see the change in Firefox 51 Aurora. Is it in the pipeline for Edge and Safari?

[Chris Harrelson]

LGTM2

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

[PhistucK]

Looks like you are using an old intent to ship template, where did you find it? It is missing some sections (interoperability risk, intent to implement thread link)...

☆PhistucK

[Rick Byers]

LGTM3

I remember there was some data on how often control characters show up on real websites, right?  But given the other browsers have already adopted this (and IIRC we said in CSSWG that we'd be willing to ship at the same time as them), I don't see any need to block this intent on hard data.

[Joe Medley]

Gang,

I have two questions and an issue. First, what version of was this behind a flag? (M47?) What version do you think this will ship in?

Now the issue. From above: "It's been an experimental web platform feature for months with no compat reports and with this change we'll now, once again, match the other browsers."

Since other browsers have already shipped this, the danger of breaking pages is probably minimal. What concerns me is that this should have had a Chrome Status entry before it went into Chrome behind a flag. 

Please us this rule of thumb in the future: If it's in Chrome Dev, Canary, Beta, or Stable in any way shape or form, it needs a status entry, and that status entry should have a version number. 

If by chance you come across a use case that doesn't fit Chrome Status (which I believe to be unlikely) please post a question on blink-dev. 

Thanks.

Joe

Joe Medley | Technical Writer, Chrome DevRel | jme...@google.com | 816-678-7195

If an API's not documented it doesn't exist.

[Emil A Eklund]

On Mon, Oct 17, 2016 at 10:15 AM, 'Joe Medley' via blink-dev
<blin...@chromium.org> wrote:
> Gang,
>
> I have two questions and an issue. First, what version of was this behind a
> flag? (M47?) What version do you think this will ship in?

M54, will likely ship in M57

> Now the issue. From above: "It's been an experimental web platform feature
> for months with no compat reports and with this change we'll now, once
> again, match the other browsers."
>
> Since other browsers have already shipped this, the danger of breaking pages
> is probably minimal. What concerns me is that this should have had a Chrome
> Status entry before it went into Chrome behind a flag.

There has been a chrome status entry (linked in original mail) since
well before this was enabled as experimental. It was also linked in
the original intent to implement thread.

[Joe Medley]

The status entry currently has no version number on it. If it did, someone has removed it. Please add it back with the label 'Behind a flag'.

Joe Medley | Technical Writer, Chrome DevRel | jme...@google.com | 816-678-7195

If an API's not documented it doesn't exist.

[Joe Medley]

Just saw the update. Thank you.

Joe Medley | Technical Writer, Chrome DevRel | jme...@google.com | 816-678-7195

If an API's not documented it doesn't exist.