W3C home > Mailing lists > Public > public-webapi@w3.org > June 2007

Re: [selectors-api] Minor comments on the spec text

From: liorean <liorean@gmail.com>
Date: Tue, 26 Jun 2007 20:12:38 +0200
Message-ID: <cee13aa30706261112j69e589e0k1f982c1710702d78@mail.gmail.com>
To: "Web APIs WG (public)" <public-webapi@w3.org>

On 26/06/07, Lachlan Hunt <lachlan.hunt@lachy.id.au> wrote:
> Lachlan Hunt wrote:
> > liorean wrote:
> >> I think it wouldn't hurt to specify that an exception should be
> >> propagated (or rethrown?) out to the caller.
> >
> > Surely, if it were necessary to state that, it should be in DOM Level 3
> > Core where DOMException is defined, instead of in each individual spec
> > that uses exceptions.
>
> It seems I initially misunderstood which exceptions this issue was
> referring to.

Sounds that way, yes. The question is about an ECMAScript exception
being passed to the application code and how the application code
should deal with that.

> If I add something like this, would that resolve this issue?
>
> | If an exception is raised by the NSResolver while resolving
> | namespaces, processing must be aborted and the exception
> | passed back to the caller.

That would resolve the issue, yes.
-- 
David "liorean" Andersson
Received on Tuesday, 26 June 2007 18:12:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:57 GMT