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

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

From: Glenn Adams <glenn@skynav.com>
Date: Sun, 7 Oct 2012 12:30:04 +0800
Message-ID: <CACQ=j+ekLFztQcXSk0FE4mDM_3a2=uH0UXQg8ie6W2xvV=hC6A@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Simon Sapin <simon.sapin@kozea.fr>, WWW Style <www-style@w3.org>
On Sun, Oct 7, 2012 at 11:50 AM, Tab Atkins Jr. <jackalmage@gmail.com>wrote:

> 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.

I'm referring to what the spec would have one do, as opposed to what UAs
actually do. Do you agree the tokenizer rule as specified would consume an
escaped NULL (whether or not a UA actually allows a NULL to get that far)?
Received on Sunday, 7 October 2012 04:30:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:22 UTC