Re: Comments on Widgets 1.0: Requirements LCWD

2008-08-19 Thread Krzysztof Maczyński
W dniu 15 sierpnia 2008 06:05 użytkownik Marcos Caceres <[EMAIL PROTECTED]> napisał: > HI Krzysztof, > Just a friendly reminder that we (WebApps) are waiting for you to > respond to the LC comments. Can you please let me know either way if > you are planning to respond or not. If you are, I would

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

2008-08-19 Thread Lachlan Hunt
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 methods that use feature strings, including: interface DOMImplementationSource

ElementTraversal support in Firefox 3.1

2008-08-19 Thread Jonas Sicking
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' property which is an NodeList of all child elements to allo

Re: [selectors-api] Investigating NSResolver Alternatives

2008-08-19 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-19 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 beh