72 messages in org.w3.public-webapiRe: ACTION-87: Selectors API
FromSent OnAttachments
Anne van KesterenFeb 25, 2006 9:11 am.htm
Daniel SchierbeckFeb 25, 2006 10:18 am 
Daniel SchierbeckFeb 25, 2006 10:23 am 
Bjoern HoehrmannFeb 25, 2006 10:43 am 
Daniel SchierbeckFeb 25, 2006 11:28 am 
Jim LeyFeb 25, 2006 11:47 am 
Ian HicksonFeb 25, 2006 3:56 pm 
Cameron McCormackFeb 25, 2006 4:46 pm 
Lachlan HuntFeb 25, 2006 4:58 pm 
Cameron McCormackFeb 25, 2006 5:00 pm 
Daniel SchierbeckFeb 25, 2006 5:24 pm 
Anne van KesterenFeb 26, 2006 2:21 am 
Cameron McCormackFeb 26, 2006 2:32 am 
Cameron McCormackFeb 26, 2006 1:03 pm 
Maciej StachowiakFeb 26, 2006 3:02 pm 
Jonas SickingFeb 28, 2006 1:57 pm 
Ian HicksonMar 6, 2006 12:33 pm 
Ian HicksonMar 6, 2006 12:35 pm 
Anne van KesterenMar 22, 2006 2:30 am 
Anne van KesterenMar 22, 2006 2:33 am 
Anne van KesterenMar 22, 2006 2:34 am 
mozerMar 22, 2006 3:15 am 
Anne van KesterenMar 22, 2006 3:58 am 
mozerMar 22, 2006 4:29 am 
Anne van KesterenMar 22, 2006 4:36 am 
Jim LeyMar 22, 2006 5:43 am 
Anne van KesterenMar 22, 2006 6:08 am 
Jim LeyMar 22, 2006 6:44 am 
Maciej StachowiakMar 22, 2006 11:16 am 
Maciej StachowiakMar 22, 2006 11:22 am 
Maciej StachowiakMar 22, 2006 11:24 am 
Robin BerjonMar 22, 2006 2:01 pm 
Maciej StachowiakMar 22, 2006 2:28 pm 
Ian HicksonMar 22, 2006 2:48 pm 
Ian HicksonMar 22, 2006 2:50 pm 
Maciej StachowiakMar 22, 2006 3:20 pm 
Jim LeyMar 22, 2006 6:16 pm 
Jim LeyMar 22, 2006 6:24 pm 
Anne van KesterenMar 23, 2006 4:27 am 
Ian HicksonMar 23, 2006 2:30 pm 
Anne van KesterenMar 25, 2006 4:36 am 
Ian HicksonMar 27, 2006 3:13 pm 
Anne van KesterenApr 3, 2006 5:45 am 
Anne van KesterenApr 3, 2006 5:51 am 
lioreanMay 12, 2006 8:49 pm 
Anne van KesterenMay 13, 2006 4:15 am 
lioreanMay 13, 2006 12:08 pm 
Anne van KesterenMay 13, 2006 12:26 pm 
lioreanMay 13, 2006 2:39 pm 
Anne van KesterenMay 14, 2006 7:20 am 
lioreanMay 14, 2006 4:21 pm 
Anne van KesterenMay 15, 2006 3:15 am 
lioreanMay 16, 2006 9:29 pm 
Anne van KesterenMay 17, 2006 5:17 am 
Lachlan HuntMay 17, 2006 6:19 am 
Anne van KesterenMay 17, 2006 6:29 am 
Jim LeyMay 17, 2006 6:35 am 
Lachlan HuntMay 17, 2006 7:02 am 
Robin BerjonMay 17, 2006 7:07 am 
Anne van KesterenMay 18, 2006 12:45 am 
Jonas SickingMay 30, 2006 3:11 pm 
Jonas SickingMay 30, 2006 3:24 pm 
Jonas SickingMay 30, 2006 3:41 pm 
Ian HicksonMay 30, 2006 3:55 pm 
Robin BerjonMay 30, 2006 4:14 pm 
Jonas SickingMay 30, 2006 5:56 pm 
Anne van KesterenJun 5, 2006 2:46 am 
Anne van KesterenJun 5, 2006 2:49 am 
Jonas SickingJun 5, 2006 12:30 pm 
Charles McCathieNevileJun 5, 2006 5:36 pm 
lioreanJun 5, 2006 6:16 pm 
Maciej StachowiakJun 5, 2006 10:40 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: ACTION-87: Selectors APIActions...
From:mozer (xmli@gmail.com)
Date:Mar 22, 2006 3:15:46 am
List:org.w3.public-webapi

Hi Anne and al.

Some precisions

in spec could we replace "selector" by "selectors" because of it is a "group of selector" ?

little typo miss a space after MUST in

"The match method, when invoked, *must* return the first Element that matches the group of selectors (selector), if any. Otherwise it *must*return null."

"if the given selector selector is an invalid selector or " should be replaced by "if the given group of selectors selector(s) contain an invalid selector or"...

Mohamed Zergaoui, Innovimax

On 3/22/06, Anne van Kesteren <ann@opera.com> wrote:

Hi Ian,

Thanks for your comments.

A new draft can be found here:

< http://dev.w3.org/cvsweb/~checkout~/2006/webapi/selectors-api/draft/selectors-api.htm?rev=1.2

Comments on the draft:

* It makes no sense for the UA to implement an interface. Objects that the UA exposes implement interfaces, not UAs.

Should be fixed.

* The UA doesn't need to expose an object that implements the NSResolver, only the author does.

Should be fixed.

* Having an interface doesn't imply behaviour -- e.g. NodeList doesn't imply that NodeList is live. You can have an object that implemnets NodeList and is not live.

DOM Level 3 Core says it's live. Per discussion on public #webapi I see that is suboptimal and if DOM Level 3 Core gets errata to make that more clear I'll reconsider it.

* IMHO getElementsBySelector() should return a live list, just like getElementsByTagName.

Implementors disliked that idea. You now agree with them, not?

* I would recommend against supporting namespaces in the first version, for simplicity.

I agree that they are probably not that much needed by authors. Therefore the argument is optional in ECMAScript bindings so it doesn't harm the scenario were people probably use it the most.

* I would recommend having getElementsBySelector and getElementsBySelectorNS if you wanted to support both, rather than using optional arguments. Some languages don't support method overloading on argument signatures and would need different numbers of arguments

anyway.

In those languages the second argument is simply required.

* There is no actual conformance criteria for what should happen when the getElementsBySelector method is invoked (the spec says "returns" not "must, when invoked, return").

Used the "suggested" language, thanks.

* The spec doesn't say _how_ to resolve the namespaces using the nsresolver argument.

I deferred this to DOM Level 3 XPath now.

* IMHO the argument to getElementsBySelector should be a "group of selectors" not a "selector" (using Selectors terminology).

Used this terminology although I don't really see the Selectors draft defining this term (using <dfn> or whatever). Could you please point it out?

* IMHO the method should not raise an exception when the selector contains a pseudo-element. It should would return an empty list.

Given that it per definition only returns Element nodes I don't see why it shouldn't raise an exception.

-- Anne van Kesteren <http://annevankesteren.nl/> <http://www.opera.com/>