W3C home > Mailing lists > Public > public-webapi@w3.org > December 2006

RE: NSResolver Re: Selectors API naming

From: Chris Wilson <Chris.Wilson@microsoft.com>
Date: Thu, 21 Dec 2006 10:47:58 -0800
Message-ID: <44FAFFCDE516434D84E6B62121DB6A4404137570@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
To: Charles McCathieNevile <chaals@opera.com>, Dave Massy <dave.massy@microsoft.com>, Web API public <public-webapi@w3.org>
CC: Anne van Kesteren <annevk@opera.com>, Tina Duff <tinad@microsoft.com>
Nope, that's what I meant.  The spec should give more examples, particularly in the simplistic cases.  The one case I wanted a definition for was if there is no doctype given on an HTML document, and there is a specific namespace given for XHTML (or whatever), does it match?  (e.g. is there a presumed doctype default for HTML in browsers, and if so what is it.  I would prefer not, BTW.)

-----Original Message-----
From: Charles McCathieNevile [mailto:chaals@opera.com] 
Sent: Thursday, December 21, 2006 10:42 AM
To: Chris Wilson; Dave Massy; Web API public
Cc: Anne van Kesteren; Tina Duff
Subject: Re: NSResolver Re: Selectors API naming

On Thu, 21 Dec 2006 19:09:17 +0100, Chris Wilson  
<Chris.Wilson@microsoft.com> wrote:

> Wow, sorry, a bunch of messages got caught in spam filter temporarily.
> I think the point was overcommunicating how this works in the spec would  
> be a really good idea, not "this doesn't work well."

Not quite sure I follow you, but If you mean "We should explain this in  
more detail" then I am with you (doubly so if you have proposed text and  
examples for the spec ;) ). If you mean something else, I am confused...



> -----Original Message-----
> From: Charles McCathieNevile [mailto:chaals@opera.com]
> Sent: Tuesday, December 19, 2006 12:59 PM
> To: Dave Massy; Web API public
> Cc: Chris Wilson; Anne van Kesteren; Tina Duff
> Subject: NSResolver Re: Selectors API naming
> On Tue, 19 Dec 2006 21:35:17 +0100, Dave Massy <Dave.Massy@microsoft.com>
> wrote:
>> It'd be great to have more detail and scenario on NSResolver. It appears
>> to allow elements within the document to have different prefixes than
>> things in the style sheet. For example if we map html as the prefix for
>> XHTML in our document then we’d write it like:
>> 	<html:table><html:tr><html:td></html:td></html:tr></html:table>
>> But then we can write a selector such as:
>> 	“h|table > h|tr > h|td”
>> With a NSResolver that maps h to the same namespace as the html in the
>> primary document. This seems potentially confusing.
> Hmm. This seems blindingly obvious to me, as something that if anyone  
> ever
> forces me to hand-code I automatically do. This is how namespaces work in
> general. Admittedly, if you are sharing code snippets amongst people who
> have no shared understanding and are not really aware of what namespace
> prefixes provide (a shorthand for a simple URI-based disambiguation
> scheme), then using this feature can be confusing. I don't see that as a
> reason to disallow the use case of simplifying my half of some code,  
> since
> there is no obvious technical problem here.
> cheers
> Chaals

   Charles McCathieNevile, Opera Software: Standards Group
   hablo español  -  je parle français  -  jeg lærer norsk
chaals@opera.com          Try Opera 9 now! http://opera.com

Received on Thursday, 21 December 2006 18:48:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:22 UTC