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: Aryeh Gregor <ayg@aryeh.name>
Date: Sun, 17 Jun 2012 16:50:49 +0300
Message-ID: <CAKA+AxnzyYdekK7y9mkXx35JkbYsnuk_Y1ou4ypvikssWb2JsQ@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: public-webapps@w3.org
On Sun, Jun 17, 2012 at 4:43 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 6/17/12 9:33 AM, Anne van Kesteren wrote:
>> Always throwing SyntaxError is probably better.
> Also probably incompatible with a depth-first recursive descent parser
> implementation.  Are we sure we want to overconstrain implementations like
> that?

I'm not sure what Anne meant, but I'd think we should just always
require SyntaxError, including for namespace errors.  Do enough people
really use namespaces that they deserve a separate exception?  CSS
itself treats namespace errors the same as syntax errors in
stylesheets (right?), so it doesn't make sense to require Selectors
APIs to distinguish them.
Received on Sunday, 17 June 2012 13:51:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:34 UTC