On 11/22/11 1:56 AM, Sean Hogan wrote:
On 22/11/11 7:14 PM, Roland Steiner wrote:
On Tue, Nov 22, 2011 at 14:19, Yehuda Katz <wyc...@gmail.com
<mailto:wyc...@gmail.com>> wrote:
Yehuda Katz
(ph) 718.877.1325 <tel:718.877.1325>
On Mon, Nov 21, 2011 at 8:34 AM, Boris Zbarsky <bzbar...@mit.edu
<mailto:bzbar...@mit.edu>> wrote:
On 11/21/11 11:31 AM, Tab Atkins Jr. wrote:
1) Make sense.
2) Not break existing content.
3) Be short.
.matches
.is
I like .is, the name jQuery uses for this purpose. Any reason not
to go with it?
IMHO 'is' seems awfully broad in meaning and doesn't very well
indicate that the parameter should be a selector. Inasmuch I like
.matches better.
Also, FWIW, an 'is' attribute on elements was/is in discussion on
this ML as one possibility to specify components.
Funnily enough, I've just been talking to the DOM5 and DOM6 API
designers and they said almost exactly the same thing.
On the the theme, Be short, are there issues with .has?
if(node.has('[role="button"]')) node.is='button';