W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2008

Re: [selectors-api] Why does the default namespace have to be resolved?

From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Date: Mon, 20 Oct 2008 11:29:01 +0200
Message-ID: <48FC4F5D.1050709@lachy.id.au>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
Cc: public-webapps@w3.org

Boris Zbarsky wrote:
> Section 6.1 of the editor's draft says:
> 
>   If the implementation does support resolving namespaces, then the
>   implementation must use the nsresolver to get the default namespace
>   for the group of selectors. If the group of selectors include
>   namespace prefixes that need to be resolved, the implementation
>   must also use it to resolve those prefixes.
> 
> I don't understand why we have the requirement in this form.  If the 
> selector string is, say "*|*" there is no need to resolve a default 
> namespace prefix, and I don't think the implementation should be 
> required to resolve it in that situation.

Since NSResolver has since been removed from the spec, I'm closing this
issue as it is no longer relevant.

-- 
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Received on Monday, 20 October 2008 09:29:40 GMT

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