On Jan 09, 2007, at 23:08, Anne van Kesteren wrote:
I updated the Selectors API specification today and added
equivalent methods for element nodes. It didn't make much sense to
me to postpone this.
I resolved the naming debate by going for:
* Document.get()
* Document.getAll()
*
I have to agree with Robin here. The new names suggested do not address
the concerns raised around the original naming in the specification.
Naming should be:
a) descriptive of the functionality
b) in line with conventions for existing DOM APIs such as
getElementbyID
Looking at the feedback
Subject
AMRe: Selectors API updates
On 1/9/07, Anne van Kesteren [EMAIL PROTECTED] wrote:
These names are short, don't clash with autocomplete and provide a
superset of the functionality given by the other get* methods.
Works for me. Thanks, Anne.
--
Robert Sayre
http://franklinmint.fm
http://mozilla.com
* Anne van Kesteren wrote:
These names are short, don't clash with autocomplete and provide a
superset of the functionality given by the other get* methods.
As an aside, there are about 30 different get... methods on Element
and/or Document nodes in DOM Core, SVG, HTML5, and your work CSS
OM
On Wed, 10 Jan 2007 19:14:46 +0100, Dave Massy [EMAIL PROTECTED]
wrote:
Looking at the feedback on
http://lists.w3.org/Archives/Public/public-webapi/ and Anne's blog entry
at http://annevankesteren.nl/2006/12/selectors-api-naming it seems that
the majority of people would agree with these
On Wed, 10 Jan 2007 20:04:29 +0100, Bjoern Hoehrmann [EMAIL PROTECTED]
wrote:
When that last issue is resolved I think the specification is ready for
Last Call (again).
The addition of the methods on Element objects is a substantive
change and Last Calls should not include substantive
On Jan 9, 2007, at 2:08 PM, Anne van Kesteren wrote:
I updated the Selectors API specification today and added
equivalent methods for element nodes. It didn't make much sense to
me to postpone this.
I resolved the naming debate by going for:
* Document.get()
* Document.getAll()
*
I updated the Selectors API specification today and added equivalent
methods for element nodes. It didn't make much sense to me to postpone
this.
I resolved the naming debate by going for:
* Document.get()
* Document.getAll()
* Element.get()
* Element.getAll()
These names are short,
