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

Re: [cssom] serializing U+0000 NULL

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 30 Nov 2015 20:20:37 -0800
Message-ID: <CAAWBYDBA=Bi-_vK=PRrixA-722Q8uxp4VChTcn2HPS24nr+PCA@mail.gmail.com>
To: Simon Pieters <simonp@opera.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>
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.

~TJ
Received on Tuesday, 1 December 2015 04:21:27 UTC

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