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: Wed, 10 Oct 2012 09:37:04 +0200
Message-ID: <507525A0.7010901@kozea.fr>
To: www-style@w3.org
Le 10/10/2012 01:58, Glenn Adams a écrit :
> it would seem a bit easier to not have to admit < \\, NUL > for
> implementation reasons; there is really no loss of functionality if this
> is not supported, since if the author really wants a NUL, then can just
> use < \\, 0, SPACE > or perhaps < \\, 0 > if the context permits.

What would exactly mean to "not admit" a sequence of codepoints? Abort 
completely the tokenizer and throw away the rest of the stylesheet, have 
the usual error-recovery, or maybe something else?

-- 
Simon Sapin
Received on Wednesday, 10 October 2012 07:37:35 GMT

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