- From: liorean <liorean@gmail.com>
- Date: Tue, 26 Jun 2007 20:12:38 +0200
- 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 UTC