W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: [selectors-api] NAMESPACE_ERR or SYNTAX_ERR when both applied

From: Simon Pieters <simonp@opera.com>
Date: Mon, 18 Jun 2012 09:42:46 +0200
To: "WebApps Working Group" <public-webapps@w3.org>, "Kang-Hao (Kenny) Lu" <kennyluck@csail.mit.edu>
Message-ID: <op.wf281kdfidj3kv@simons-macbook-pro.local>
On Sun, 17 Jun 2012 13:10:11 +0200, Kang-Hao (Kenny) Lu  
<kennyluck@csail.mit.edu> wrote:

> 1. Explicitly undefine this case.

That would not be my preference.


> 2. Spec IE9, Firefox13 and Opera12alpha's behavior
>
> Roughly speaking, the choice is "an invalid token or '|' whichever comes
> first", but I'd note that in the corner case

These are valid:

|a
*|a


My proposed spec change:

>   # If the group of selectors include namespace prefixes that need to
>   # be resolved, the implementation must raise a NAMESPACE_ERR
>   # exception.

s/NAMESPACE_ERR/SYNTAX_ERR/

-- 
Simon Pieters
Opera Software
Received on Monday, 18 June 2012 07:44:25 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:52 GMT