Comments on: Native CSS selectors with querySelector http://ajaxian.com/archives/native-css-selectors-with-queryselector Cleaning up the web with Ajax Thu, 17 May 2012 07:43:39 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: jdalton http://ajaxian.com/archives/native-css-selectors-with-queryselector/comment-page-1#comment-261293 jdalton Tue, 12 Feb 2008 03:45:11 +0000 http://ajaxian.com/?p=3319#comment-261293 Ticket and patch submitted for Prototype 1.6.0.2 as well: http://dev.rubyonrails.org/ticket/11085 Ticket and patch submitted for Prototype 1.6.0.2 as well:
http://dev.rubyonrails.org/ticket/11085

]]> By: Hans Schmucker http://ajaxian.com/archives/native-css-selectors-with-queryselector/comment-page-1#comment-261291 Hans Schmucker Mon, 11 Feb 2008 23:23:51 +0000 http://ajaxian.com/?p=3319#comment-261291 Just out of curiosity.... what does document.querySelector(":hover"); actually return? I mean, not only can links be hovered, but also the body node ... which means that you should end up with the body node whenever the mouse is inside the window. But I've got the strange suspicion that the result will be different.... Just out of curiosity…. what does document.querySelector(“:hover”); actually return? I mean, not only can links be hovered, but also the body node … which means that you should end up with the body node whenever the mouse is inside the window. But I’ve got the strange suspicion that the result will be different….

]]> By: slightlyoff http://ajaxian.com/archives/native-css-selectors-with-queryselector/comment-page-1#comment-261288 slightlyoff Mon, 11 Feb 2008 21:35:27 +0000 http://ajaxian.com/?p=3319#comment-261288 ...and Dojo is updated to support it, although it does seem to make the nightly crash on our test pages. http://trac.dojotoolkit.org/ticket/5832 Regards …and Dojo is updated to support it, although it does seem to make the nightly crash on our test pages.

http://trac.dojotoolkit.org/ticket/5832

Regards

]]> By: efattal http://ajaxian.com/archives/native-css-selectors-with-queryselector/comment-page-1#comment-261284 efattal Mon, 11 Feb 2008 20:02:05 +0000 http://ajaxian.com/?p=3319#comment-261284 It looks like your "Native" library is missing in the performance test page. Shouldn't it be instead of dummy.js? It looks like your “Native” library is missing in the performance test page. Shouldn’t it be instead of dummy.js?

]]> By: Eric Anderson http://ajaxian.com/archives/native-css-selectors-with-queryselector/comment-page-1#comment-261275 Eric Anderson Mon, 11 Feb 2008 14:51:03 +0000 http://ajaxian.com/?p=3319#comment-261275 Evaluating it 250 times is meant to avoid difference in performance due to other things happening on the system (garbage collection, other programs, etc.). If it only ran it once you may not be getting an accurate result. Plus the test would run so fast you may also encounter slight errors in the timing. Running it 250 times magnifies the results making those slight errors somewhat negligible. Evaluating it 250 times is meant to avoid difference in performance due to other things happening on the system (garbage collection, other programs, etc.). If it only ran it once you may not be getting an accurate result. Plus the test would run so fast you may also encounter slight errors in the timing. Running it 250 times magnifies the results making those slight errors somewhat negligible.

]]> By: Cloudream http://ajaxian.com/archives/native-css-selectors-with-queryselector/comment-page-1#comment-261273 Cloudream Mon, 11 Feb 2008 13:29:32 +0000 http://ajaxian.com/?p=3319#comment-261273 who will query elements 250 times without evaluating results into a cache? who will query elements 250 times without evaluating results into a cache?

]]>