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

On Sat, Oct 6, 2012 at 6:56 PM, Glenn Adams <> wrote:
> OK, but as the current syntax is written for the escape non-terminal, it
> will definitely match an escaped NULL. I would have preferred to see NULL
> excluded from escaping, i.e., always treating it as EOF/EOS for the purpose
> of defining normative tokenization processing.

Just depends on how browsers do it.


Received on Sunday, 7 October 2012 03:51:17 UTC