- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Wed, 09 Jul 2008 10:10:17 -0400
- To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
- CC: Webapps <public-webapps@w3.org>
Lachlan Hunt wrote: > * Authors may use *|foo or |foo without providing an NSResolver > * Defined that namespace prefixes only need to be resolved when > the namespace component is neither * or empty. This all makes sense. > * Defined that implementations must support * or empty namespace > components, regardless of whether or not they support resolving > prefixes. This does not. If an implementation has not CSS3 Namespaces support, then the '|' symbol is unrecognized in a selector, and parsing the selector will raise a SYNTAX_ERR per this specification. This is the behavior IE8 has, and seems correct to me (well, modulo the fact that they in fact do not throw on a non-null NSResolver). On a separate note, and going back to the earlier discussion about whether NSResolver should be replaced to something else... that discussion seemed to not go anywhere, and I'd like to actually expose namespaces in the Gecko implementation of querySelector(All), so I will be implementing NSResolver as currently specified. -Boris
Received on Wednesday, 9 July 2008 14:11:03 UTC