Comments on: querySelectorAll is coming fast http://ajaxian.com/archives/queryselectorall-is-coming-fast Cleaning up the web with Ajax Thu, 09 Feb 2012 06:55:33 +0000 hourly 1 http://wordpress.org/?v=3.2 By: randomrandom http://ajaxian.com/archives/queryselectorall-is-coming-fast/comment-page-1#comment-266877 randomrandom Sun, 24 Aug 2008 19:47:35 +0000 http://ajaxian.com/?p=4153#comment-266877 Second that. A "query selector" would be something that selects queries. To be more specific, it only works with CSS selectors. In Hpricot you can use either XPath or CSS selectors, which is much nicer. Second that. A “query selector” would be something that selects queries. To be more specific, it only works with CSS selectors. In Hpricot you can use either XPath or CSS selectors, which is much nicer.

]]> By: Jaaap http://ajaxian.com/archives/queryselectorall-is-coming-fast/comment-page-1#comment-266869 Jaaap Sat, 23 Aug 2008 23:17:04 +0000 http://ajaxian.com/?p=4153#comment-266869 I've been wondering what "querySelector" meant since the first time i read it (just ignored it since it sounds boring). Now i read that it just means getElementsBySelector() whcih immediately tells anyone who ever used getElementById or getElementsByTagNamw what it does. Why in the world would you use a puzzling name like querySelector in stead of a self-explanatory name like getElementBySelector? I’ve been wondering what “querySelector” meant since the first time i read it (just ignored it since it sounds boring).
Now i read that it just means getElementsBySelector() whcih immediately tells anyone who ever used getElementById or getElementsByTagNamw what it does.

Why in the world would you use a puzzling name like querySelector in stead of a self-explanatory name like getElementBySelector?

]]>