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

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

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Mon, 8 Oct 2012 16:11:17 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>, Glenn Adams <glenn@skynav.com>
CC: Simon Sapin <simon.sapin@kozea.fr>, WWW Style <www-style@w3.org>
Message-ID: <3C4041FF83E1E04A986B6DC50F0178291BE4E963@TK5EX14MBXC227.redmond.corp.microsoft.com>

[Tab Atkins Jr.:]
> 
> 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.
> 
If content legitimately depends on NULL byte handling then implementations 
are certainly the first step. More important than what they do is why. I 
also wouldn't mind hearing more about why Glenn prefers NULL to be excluded 
from escaping.

Received on Monday, 8 October 2012 16:11:51 GMT

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