Re: [css2.1] tokenizer syntax - handling escaped null in badstring from Tab Atkins Jr. on 2012-10-07 (www-style@w3.org from October 2012)

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Sat, 6 Oct 2012 20:50:29 -0700
To: Glenn Adams <glenn@skynav.com>
Cc: Simon Sapin <simon.sapin@kozea.fr>, WWW Style <www-style@w3.org>
Message-ID: <CAAWBYDBODPEX_Dz7PCmfv_gWTCTt0adxYyV8jGtWgoDjb7+PHA@mail.gmail.com>

On Sat, Oct 6, 2012 at 6:56 PM, Glenn Adams <glenn@skynav.com> 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.

~TJ

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