Re: [cssom] serializing U+0000 NULL

On Thu, 03 Dec 2015 09:20:58 +0100, Simon Pieters <simonp@opera.com> wrote:

> On Tue, 01 Dec 2015 13:01:16 +0100, Simon Pieters <simonp@opera.com>  
> wrote:
>
>>>> 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!
>
> Hmm. I noticed now that U+FFFD is not escaped by CSSOM's rules, so the  
> above still doesn't hold. It should just be the U+FFFD character. Not  
> escaping is consistent with what browsers do for e.g.  
> CSSRule#selectorText. Will fix now. Sorry for not checking this more  
> throughly earlier!

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

-- 
Simon Pieters
Opera Software

Received on Thursday, 3 December 2015 08:25:35 UTC