querySelectorAll is enabled in IE9, checkout "ie9 testdrive". On 28 May 2011 19:50, "nathanJsweet" <[email protected]> wrote:
So I've been messing around with querySelectorAll. I've published a blog post about it which can be found at "nathansweet.me/ queryselectorall", though I'm not really plugging the post, which actually doesn't have so much information concerning the method as it does a link to a page I've created that tests the method. I'm asking anybody in this group who is interested take a look at this page (it can be found at "nathansweet.me/queryselectorall- rundown") and email me, respond to this post, or comment on the blog post any other selector ideas they can come up with. My goal would be to come up with an exhaustive list of selectors that I could then run through a multitude of browsers (I would, of course, share the results). I've already come up with some interesting failures that shouldn't be occurring, and I'm also interested to hear from people who've worked with the method extensively. Also am I wrong in thinking that since querySelectorAll isn't implemented in IE that it will always return only elements? Thus, is it safe to do Array.prototype.slice.call on any nodelist returned by querySelectorAll? I haven't thought of a case yet where this wouldn't be a bad idea, let me know. Also, if nobody helps it's no big deal, as I will be adding selectors to it over the coming weeks, so if you're into bookmarking it might be worth coming back for a second or third look. -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected] -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
