W3C home > Mailing lists > Public > www-style@w3.org > September 2015

Re: [css-text] Control Characters Roll Call on implementation

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 10 Sep 2015 16:15:28 -0700
Message-ID: <CAAWBYDBYR6SBcft_iqUOYsNGw=_0uEORefPdVn+dAgut=xGt_g@mail.gmail.com>
To: Greg Whitworth <gwhit@microsoft.com>
Cc: David Baron <dbaron@dbaron.org>, Dean Jackson <dino@apple.com>, Tab Atkins <tabatkins@google.com>, "www-style@w3.org" <www-style@w3.org>
On Thu, Sep 10, 2015 at 1:21 PM, Greg Whitworth <gwhit@microsoft.com> wrote:
> Hello everyone,
> As I brought up at recent F2F, and I plan to bring up again at TPAC, we all agreed[1] to implement behind a flag the breaking change stated in CSS Text L3 to render control characters.
>     # Control characters (Unicode category Cc) other than tab (U+0009), line feed (U+000A), 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. The UA may use a glyph provided by a font specifically
>     # for the control character, substitute the glyphs provided for the corresponding symbol in the Control Pictures block, generate a visual representation of its
>     # codepoint value, or use some other method to provide an appropriate visible glyph. As required by [UNICODE], unsupported Default_ignorable characters
>     # must be ignored for rendering.
> We have implemented this in Microsoft Edge for all C0 and if it did not already have a hex box in the selected font we are using U+25AF (White Vertical Rectangle). One thing of note is that we noticed all browsers throw away the C1 control characters during HTML parsing so this replacement isn't possible. If the other UAs can confirm this we should adjust the language in the text to only change the C0 control characters and ensure that your HTML parser is disposing of the C1 block.
> Here are bugs for the dev work in each browser:
> Mozilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1099557
> Webkit: Can't seem to find one (Dean, can you please get me one)
> Blink: Can't find one (Tab, can you please get me one)
> Microsoft: Implemented behind a flag, I'll provide an email once it's available in an insider preview
> I want to **reiterate** that while this is not a monumental change, this is actually an important practice for all of us to work together on a breaking change and potentially increase this to clean up the web platform in the future.
> Please let me know where you development status is and if you expect to have the development done by October (TPAC). Remember, it does not have to ship, just be completed.

I've been poking at Emil for a while, and he just sent an Intent To
Implement <https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/uIc2ZvLQOHw>
and a bug <https://code.google.com/p/chromium/issues/detail?id=530342>.
He'd already implemented this a while back (predating our agreement to
do it together) but had it reverted, so the code is already ready to
go. Assuming we target Chrome 47 as planned, it'll hit stable on
December 1.

Received on Thursday, 10 September 2015 23:16:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:56 UTC