ISSUE-114 - Public View

Return Values from NSResolver

State:

CLOSED

Product:

Selectors API

Raised by:

Lachlan Hunt

Opened on:

2007-04-02

Description:

There's a few things the Selectors API spec currently doesn't seem to define in
regards to the NSResolver.

1. What should the author make the nsresolver return for the default namespace
when there isn't one?  null, void, "" or either?

2. Given that the UA can never be sure what the author will actually return, the
spec needs to define how the UA must handle all possible return values.

In #webapi, Björn said in relation to #1:

  "well "no namespace" in the dom is indicated by a DOMString that's either
   empty or null, but indeed the draft doesn't seem to note that."

In relation to #2, he said:

  "that's something for the dom/ecmascript clarifications specification
   because the group agreed that that specification would say how to
   handle e.g. methods that expect a DOMString but the script passes
   something else.  and here the only difference is method-parameter
   vs function return value

  "whether null/empty string is actually unexpected depends on whether
   css3-namespaces allows setting up a prefix for "no namespace"
   like, whether @namespace foo ""; is allowed."

Note: Some of these links may be accessible only to W3C Members.

Related emails:

1. ISSUE-114: Return Values from NSResolver (from dean+cgi@w3.org on 2007-04-02)
2. Re: ISSUE-114: Return Values from NSResolver (from annevk@opera.com on 2007-04-02)

Related notes: