Sean Hogan wrote:
Lachlan Hunt wrote:
Sean Hogan wrote:
Gregory Reimer (the author of reglib) points out that
Element.matchesSelector would be useful for event delegation.
See http://blogs.sun.com/greimer/entry/opera_10_will_suport_selector
It would also neatly tie in with NodeFilter in
Sean Hogan wrote:
- All the getElement* selectors are matched by straight-forward ways for
checking if an element-node matches the desired constraint.
e.g. getElementsByTagName and tagName, getElementById and id,
getElementsByClassName and className / classList
Honestly, className is not a
Gregory Reimer (the author of reglib) points out that
Element.matchesSelector would be useful for event delegation.
See http://blogs.sun.com/greimer/entry/opera_10_will_suport_selector
It would also neatly tie in with NodeFilter in DOM-Traversal,
facilitating something like a live
Sean Hogan wrote:
Gregory Reimer (the author of reglib) points out that
Element.matchesSelector would be useful for event delegation.
See http://blogs.sun.com/greimer/entry/opera_10_will_suport_selector
It would also neatly tie in with NodeFilter in DOM-Traversal,
facilitating something like
Lachlan Hunt:
OK, I have updated the spec based on this suggestion. You can review
the changes in the latest editor's draft.
http://dev.w3.org/2006/webapi/selectors-api/#nodeselector
Please let me know if you are satisfied with this response.
I’m satisfied with the response.
--
Cameron McCormack:
* In section 6, I don’t think it’s necessary to explicitly mention
undefined, since it’s already handled by the annotation in the
IDL. If you do want to include this in the prose, I think it
needs to be qualified to say that this applies to an ECMAScript
Lachlan Hunt [EMAIL PROTECTED] wrote:
Stewart Brodie wrote:
[a few issues snipped]
[see
http://lists.w3.org/Archives/Public/public-webapps/2008OctDec/0216.html ]
Thank you. I'd be pleased to see this document progress to LC.
--
Stewart Brodie
Software Engineer
ANT Software Limited
Cameron McCormack wrote:
* In the first sentence of section 6, I’d do /either/any of/, since there
are more than two interfaces listed.
Fixed.
* There’s a newer Web IDL WD available than the one referenced (with
the new name) so it might be good to reference that. Then you can
Cameron McCormack:
* In section 6, I don’t think it’s necessary to explicitly mention
undefined, since it’s already handled by the annotation in the IDL.
If you do want to include this in the prose, I think it needs to be
qualified to say that this applies to an ECMAScript language
Hear hear!
Charles McCathieNevile wrote:
Hi,
Lachy thinks the latest editor's draft[1] is ready for Last Call, after
responding to all the comments from last time (and removing the
NSResolver). The disposition of comments[2] explains what happened to
those comments.
So this is a call
Kartikaya Gupta [EMAIL PROTECTED] wrote:
On Fri, 31 Oct 2008 16:06:23 +0100, Charles McCathieNevile
[EMAIL PROTECTED] wrote:
So this is a call for Consensus to publish the Editor's Draft [1] of the
Selectors API spec as a Last Call. Please respond before Monday November
10. As always,
Kartikaya Gupta wrote:
On Fri, 31 Oct 2008 16:06:23 +0100, Charles McCathieNevile
[EMAIL PROTECTED] wrote:
[1] http://dev.w3.org/2006/webapi/selectors-api/ [2]
Is it just me or is the scope element somewhat under-defined in the
spec? The only mentions of it are in this sentence:
If the
Stewart Brodie wrote:
1) What is the scope element for - it's only mentioned in one sentence?
That statement has now been commented out (see my previous mail [1])
2) Is an empty string actually a valid selector? If not, then the whole
null/undefined is an empty string discussion is
I support the publication as Last Call.
On Oct 31, 2008, at 8:06 AM, Charles McCathieNevile wrote:
Hi,
Lachy thinks the latest editor's draft[1] is ready for Last Call,
after responding to all the comments from last time (and removing
the NSResolver). The disposition of comments[2]
Charles McCathieNevile:
So this is a call for Consensus to publish the Editor's Draft [1] of the
Selectors API spec as a Last Call. Please respond before Monday November
10. As always, silence is taken as assent but an explicit response is
preferred.
I’m in favour of publishing.
A few
15 matches
Mail list logo
