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

Re: [cssom] serializing U+0000 NULL

From: Simon Pieters <simonp@opera.com>
Date: Tue, 01 Dec 2015 13:01:16 +0100
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: "www-style list" <www-style@w3.org>, "Richard Gibson" <richard.gibson@gmail.com>, "Glenn Adams" <glenn@skynav.com>, "Boris Zbarsky" <bzbarsky@mit.edu>, "Mathias Bynens" <mathiasb@opera.com>
Message-ID: <op.x8yroea6idj3kv@simons-mbp>
On Tue, 01 Dec 2015 05:20:37 +0100, Tab Atkins Jr. <jackalmage@gmail.com>  
wrote:

> On Mon, Nov 30, 2015 at 5:18 AM, Simon Pieters <simonp@opera.com> wrote:
>> On Sun, 29 Nov 2015 02:10:41 +0100, Tab Atkins Jr.  
>> <jackalmage@gmail.com>
>> wrote:
>>> Since all CSS parsing accepts U+0000 or the "\0" escape sequence, and
>>> just converts it to U+FFFD, CSS.escape() should allow it as well.  I'm
>>> fine with doing an eager replacement with U+FFFD, or else just
>>> escaping it as \0, whichever is simpler in the spec.
>>
>>
>> Thanks. They're both simple to spec, the main difference is how it
>> round-trips. If you serialize as \0, then this does not hold:
>>
>>     CSS.escape(foo) ===  
>> CSS.escape(parseAComponentValue(CSS.escape(foo)))
>
> Sure, then lets serialize it as U+FFFD.

Fixed:  
https://github.com/w3c/csswg-drafts/commit/c2028630eaabcd07573ba4df11b8e8ecf653eeaf

Thanks Richard!

-- 
Simon Pieters
Opera Software
Received on Tuesday, 1 December 2015 12:01:48 UTC

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