Re: [selectors-api] Names of querySelector() and querySelectorAll() methods

[Dodger]

I realise it's too late, but I thought I'd add my +1 anyway.

I like Gavin's suggestion of selectElement() / selectElements()

getElement() / getElements() could also have been used for consistency
with the existing element selection function names.

. oh well. :-)

P.S. Could someone point me to the "long debates about naming" that João
referred to? I tried searching without success. Thanks.

Re: [selectors-api] Names of querySelector() and querySelectorAll() methods

[Lachlan Hunt]

Gavin Kistner wrote:

I find these names rather cumbersome and not very self-explanatory.


I agree.

Though it may be far too late for this suggestion, I would suggest that 
they should be something such as:


findNode()/findNodes() or findNode()/findAllNodes()
selectNode()/selectNodes() or selectNode()/selectAllNodes()
findBySelector()/findAllBySelector()


However, unfortunately, given the significant amount of prior discussion 
of this issue and the formal process which led to the selection of the 
current names; and the fact that we have implementations due to be 
released in upcoming versions of each of the 4 major browsers, changing 
the name at this stage is not possible.


Please let me know whether or not you are satisfied with this response.

--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/

Re: [selectors-api] Names of querySelector() and querySelectorAll() methods

[João Eiras]

Search the archives. There were long debates about naming.
In the end, the ones you see where choosen.

On , Gavin Kistner <[EMAIL PROTECTED]> wrote:



On Nov 18, 2008, at 9:32 PM, Gavin Kistner wrote:

I find these names rather cumbersome and not very self-explanatory.

Though it may be far too late for this suggestion, I would suggest that  
they should be something such as:


findNode()/findNodes() or findNode()/findAllNodes()
selectNode()/selectNodes() or selectNode()/selectAllNodes()
findBySelector()/findAllBySelector()


Er, please replace all instances of Node with Element in the above.  
Dunno what I was smoking.


And 2 more:
elementFromSelector()/elementsFromSelector()

Re: [selectors-api] Names of querySelector() and querySelectorAll() methods

[Gavin Kistner]

On Nov 18, 2008, at 9:32 PM, Gavin Kistner wrote:

I find these names rather cumbersome and not very self-explanatory.

Though it may be far too late for this suggestion, I would suggest  
that they should be something such as:


findNode()/findNodes() or findNode()/findAllNodes()
selectNode()/selectNodes() or selectNode()/selectAllNodes()
findBySelector()/findAllBySelector()


Er, please replace all instances of Node with Element in the above.  
Dunno what I was smoking.


And 2 more:
elementFromSelector()/elementsFromSelector()

[selectors-api] Names of querySelector() and querySelectorAll() methods

[Gavin Kistner]

I find these names rather cumbersome and not very self-explanatory.

Though it may be far too late for this suggestion, I would suggest  
that they should be something such as:


findNode()/findNodes() or findNode()/findAllNodes()
selectNode()/selectNodes() or selectNode()/selectAllNodes()
findBySelector()/findAllBySelector()