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

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

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Sat, 6 Oct 2012 09:33:27 -0700
Message-ID: <CAAWBYDDP-8zpPB_-WDPPzatTwLu6nEA=BM5QOZeCupAhPaXmRA@mail.gmail.com>
To: Glenn Adams <glenn@skynav.com>
Cc: W3C Style <www-style@w3.org>
On Fri, Oct 5, 2012 at 8:58 PM, Glenn Adams <glenn@skynav.com> wrote:
> 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

This is currently undefined, because I haven't yet tested browsers to
see what their handling is.  It may be that browsers auto-convert or
auto-remove NULs, I dunno.

~TJ
Received on Saturday, 6 October 2012 16:34:14 GMT

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