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

Re: Error Parsing

From: Ian Hickson <ian@hixie.ch>
Date: Sat, 23 Oct 2004 18:05:31 +0000 (UTC)
To: David Woolley <david@djwhome.demon.co.uk>
Cc: www-style@w3.org
Message-ID: <Pine.LNX.4.61.0410231801030.26459@dhalsim.dreamhost.com>

On Sat, 23 Oct 2004, Ian Hickson wrote:
> > 
> > Which in turn is because the grammar requires properly nested and 
> > closed structures, but the obvious intention is that rules be actioned 
> > as soon as they have been completely read.
> 
> Right -- it's definitely intended for CSS to be parsable with no more 
> than one character look-ahead, so anything that implies otherwise is 
> most probably incorrect.

Er, actually dbaron just pointed out to me that that's not quite true; 
with namespaced attribute selectors you have to do two-character lookahead 
to determine if it is a namespace prefix for an attribute name, or an 
attribute name for a dash-match selector.

   [foo|=bar]
   [foo|bar|=baz]

So it is really more like one-token lookahead, treating /* and */ as 
separate tokens. Except that's not what the grammar says... Ahem.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Saturday, 23 October 2004 18:05:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:34 GMT