W3C home > Mailing lists > Public > www-style@w3.org > October 2012

Re: [css2.1] tokenizer syntax - handling escaped null in badstring

From: Simon Sapin <simon.sapin@kozea.fr>
Date: Sat, 06 Oct 2012 12:32:39 +0200
Message-ID: <507008C7.604@kozea.fr>
To: Glenn Adams <glenn@skynav.com>
CC: WWW Style <www-style@w3.org>
Le 06/10/2012 05:58, Glenn Adams a écrit :
> The current tokenizer syntax [1] specifies:
>
> escape		{unicode}|\\[^\r\n\f0-9a-f]
> badstring1      \"([^\n\r\f\\"]|\\{nl}|{escape})*\\?
>
> Given the following input string:
>
> < U+0022 (QUOTATION MARK), U+005C (REVERSE SOLIDUS), U+0000 (NULL) >
>
> Does the < U+005C, U+0000 > match escape or does it match the final \\?
> ? That is, should U+0000 be treated as an escapable character or as EOF
> (EOS)? The above grammar suggests the former.
>
> [1] http://www.w3.org/TR/CSS2/grammar.html


The closest spec text I could find is in §4.1.3:

> (It is undefined in CSS 2.1 what happens if a style sheet does
> contain a character with Unicode codepoint zero.)

Although it is in a paragraph about hexadecimal escapes, I guess it 
could apply to you example too.

-- 
Simon Sapin
Received on Saturday, 6 October 2012 10:33:15 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:01 GMT