Re: [selectors-api] Investigating NSResolver Alternatives

2008-08-20 Thread Boris Zbarsky
Lachlan Hunt wrote: The way I see it, all current impls should throw something if more than one arg is passed Which exception should be thrown? Is this something I should define in this spec, or is it something for WebIDL or some other spec to deal with? Honestly, I don't care much on that

Re: [selectors-api] Investigating NSResolver Alternatives

2008-08-20 Thread Boris Zbarsky
Lachlan Hunt wrote: The developers implementing this in Opera has given me feedback saying that this shouldn't throw an exception because JS allows additional arguments to be passed to any method, including other DOM APIs, like getElementById(), etc. Is there a good reason why this should

Re: [selectors-api] Investigating NSResolver Alternatives

2008-08-20 Thread Jonas Sicking
Boris Zbarsky wrote: Lachlan Hunt wrote: The developers implementing this in Opera has given me feedback saying that this shouldn't throw an exception because JS allows additional arguments to be passed to any method, including other DOM APIs, like getElementById(), etc. Is there a good

Re: ElementTraversal support in Firefox 3.1

2008-08-20 Thread Anne van Kesteren
On Wed, 20 Aug 2008 00:08:01 +0200, Jonas Sicking [EMAIL PROTECTED] wrote: I just landed support for ElementTraversal in firefox. This will be available in tomorrow nightlies, as well as the upcoming Firefox 3.1 Alpha 2 release that should be out soon. On top of this we also implement a

Re: [selectors-api] Investigating NSResolver Alternatives

2008-08-20 Thread Anne van Kesteren
On Wed, 20 Aug 2008 08:26:30 +0200, Boris Zbarsky [EMAIL PROTECTED] wrote: Lachlan Hunt wrote: The way I see it, all current impls should throw something if more than one arg is passed Which exception should be thrown? Is this something I should define in this spec, or is it something for

Re: [selectors-api] What DOM feature Selectors API belongs to?

2008-08-20 Thread Anne van Kesteren
On Tue, 19 Aug 2008 16:35:52 +0200, Lachlan Hunt [EMAIL PROTECTED] wrote: Lachlan Hunt wrote: I have now added a mandatory feature string. http://dev.w3.org/2006/webapi/selectors-api/#dom-feature It's been suggested to me that the spec should say something about support for the other

Re: [selectors-api] Investigating NSResolver Alternatives

2008-08-20 Thread Lachlan Hunt
Jonas Sicking wrote: Boris Zbarsky wrote: Of course not throwing on extra arguments is indeed the easy path to implementation (and is what Gecko will be shipping, it looks like), so as long as you can live with the results as a spec writer it's all good by me. I think we should follow

[widgets] Agenda for 21 August 2008 Voice Conference

2008-08-20 Thread Arthur Barstow
Below is the agenda for the August 21 Widgets Voice Conference (VC). Logistics: Time: 07:00 Boston; 13:00 Paris; 20:00 Tokyo; 21:00 Brisbane Duration = 60 minutes Zakim Bridge +1.617.761.6200, conference 9231 (WAF1) IRC channel = #wam; irc.w3.org:6665 Confidentiality of minutes =

Re: ElementTraversal support in Firefox 3.1

2008-08-20 Thread Doug Schepers
Hi, Jonas- Jonas Sicking wrote (on 8/20/08 12:08 AM): I just landed support for ElementTraversal in firefox. This will be available in tomorrow nightlies, as well as the upcoming Firefox 3.1 Alpha 2 release that should be out soon. Awesome. Thanks! I'll try to get a test suite out soon.

Re: ElementTraversal support in Firefox 3.1

2008-08-20 Thread Sam Weinig
On Aug 19, 2008, at 3:08 PM, Jonas Sicking wrote: Hi all, I just landed support for ElementTraversal in firefox. This will be available in tomorrow nightlies, as well as the upcoming Firefox 3.1 Alpha 2 release that should be out soon. On top of this we also implement a 'children'