Re: NSResolver Re: Selectors API naming

2006-12-22 Thread Charles McCathieNevile
On Thu, 21 Dec 2006 23:15:09 +0100, Anne van Kesteren [EMAIL PROTECTED] wrote: On Thu, 21 Dec 2006 23:09:46 +0100, Chris Wilson [EMAIL PROTECTED] wrote: Sorry. I should be saying what namespace URI is an HTML document in? As I said before, currently implementations set the namespaceURI

RE: NSResolver Re: Selectors API naming

2006-12-22 Thread Chris Wilson
: Tina Duff Subject: Re: NSResolver Re: Selectors API naming On Thu, 21 Dec 2006 23:15:09 +0100, Anne van Kesteren [EMAIL PROTECTED] wrote: On Thu, 21 Dec 2006 23:09:46 +0100, Chris Wilson [EMAIL PROTECTED] wrote: Sorry. I should be saying what namespace URI is an HTML document in? As I said

Re: NSResolver Re: Selectors API naming

2006-12-22 Thread Maciej Stachowiak
On Dec 21, 2006, at 2:09 PM, Chris Wilson wrote: Sorry. I should be saying what namespace URI is an HTML document in? In my opinion, it is the job of whatever working group is responsible for HTML to decide this. Regards, Maciej

Re: NSResolver Re: Selectors API naming (off-topic)

2006-12-22 Thread Ian Hickson
On Fri, 22 Dec 2006, Charles McCathieNevile wrote: ([...] I understand why [the CSSWG] have special-cased HTML, although it isn't something that strikes me as a brilliant architectural principle in general and I am wondering what the pros and cons are of going further along those lines).

RE: NSResolver Re: Selectors API naming

2006-12-21 Thread Chris Wilson
, 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 [EMAIL PROTECTED] wrote: It'd be great to have more detail and scenario on NSResolver. It appears

Re: NSResolver Re: Selectors API naming

2006-12-21 Thread Charles McCathieNevile
PROTECTED] 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 [EMAIL PROTECTED] wrote: It'd be great to have more detail and scenario

RE: NSResolver Re: Selectors API naming

2006-12-21 Thread Chris Wilson
Subject: Re: NSResolver Re: Selectors API naming On Thu, 21 Dec 2006 19:09:17 +0100, Chris Wilson [EMAIL PROTECTED] 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

RE: NSResolver Re: Selectors API naming

2006-12-21 Thread Chris Wilson
for the last ten years is. -Original Message- From: Anne van Kesteren [mailto:[EMAIL PROTECTED] Sent: Thursday, December 21, 2006 12:36 PM To: Chris Wilson; Charles McCathieNevile; Dave Massy; Web API WG (public) Cc: Tina Duff Subject: Re: NSResolver Re: Selectors API naming On Thu, 21 Dec

Re: NSResolver Re: Selectors API naming

2006-12-21 Thread Anne van Kesteren
On Thu, 21 Dec 2006 22:25:11 +0100, Chris Wilson [EMAIL PROTECTED] wrote: I don't care about the particular conclusion. For the purposes of interoperability across implementations (and that IS the point of creating a standard, right?) I believe it absolutely should be defined, and is

RE: NSResolver Re: Selectors API naming

2006-12-21 Thread Chris Wilson
; Dave Massy; Web API WG (public) Cc: Tina Duff Subject: Re: NSResolver Re: Selectors API naming On Thu, 21 Dec 2006 22:25:11 +0100, Chris Wilson [EMAIL PROTECTED] wrote: I don't care about the particular conclusion. For the purposes of interoperability across implementations

Re: NSResolver Re: Selectors API naming

2006-12-21 Thread Anne van Kesteren
On Thu, 21 Dec 2006 22:57:55 +0100, Chris Wilson [EMAIL PROTECTED] wrote: Whose job is it in the W3C? (This isn't how you transform HTML into a DOM - it's what doctype do you presume when it's not there?) DOCTYPEs? DOCTYPEs have two use cases on the web as far as I know: 1. In HTML

RE: NSResolver Re: Selectors API naming

2006-12-21 Thread Chris Wilson
: NSResolver Re: Selectors API naming On Thu, 21 Dec 2006 22:57:55 +0100, Chris Wilson [EMAIL PROTECTED] wrote: Whose job is it in the W3C? (This isn't how you transform HTML into a DOM - it's what doctype do you presume when it's not there?) DOCTYPEs? DOCTYPEs have two use cases on the web as far

Re: NSResolver Re: Selectors API naming

2006-12-21 Thread Anne van Kesteren
On Thu, 21 Dec 2006 23:09:46 +0100, Chris Wilson [EMAIL PROTECTED] wrote: Sorry. I should be saying what namespace URI is an HTML document in? As I said before, currently implementations set the namespaceURI attribute of elements to null for documents parsed with an HTML parser. The

RE: NSResolver Re: Selectors API naming

2006-12-21 Thread Chris Wilson
: Selectors API naming On Thu, 21 Dec 2006 23:09:46 +0100, Chris Wilson [EMAIL PROTECTED] wrote: Sorry. I should be saying what namespace URI is an HTML document in? As I said before, currently implementations set the namespaceURI attribute of elements to null for documents parsed with an HTML

Re: NSResolver Re: Selectors API naming

2006-12-21 Thread Anne van Kesteren
On Thu, 21 Dec 2006 23:19:09 +0100, Chris Wilson [EMAIL PROTECTED] wrote: So even a quirksmode document is in the xhtml namespace? I think that's the plan, yes. That all documents parsed with an HTML parser will return a DOM with namespaced element nodes. (There's still an open question

NSResolver Re: Selectors API naming

2006-12-19 Thread Charles McCathieNevile
On Tue, 19 Dec 2006 21:35:17 +0100, Dave Massy [EMAIL PROTECTED] 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