Comments on: .className vs. .style http://webkit.org/blog/13/classname-vs-style/ All about WebKit development Sat, 21 Nov 2009 23:00:28 -0800 http://wordpress.org/?v=2.8.5 hourly 1 By: surfsurf http://webkit.org/blog/13/classname-vs-style/comment-page-1/#comment-96 surfsurf Sat, 13 Aug 2005 00:28:14 +0000 http://webkit.opendarwin.org/blog/?p=13#comment-96 What do you say to the following performance tip from http://www.devnewz.com/devnewz-3-20030514OptimizingJavaScriptforExecutionSpeed.html ? Is he right? NodeLists are lists of elements from object properties like .childNodes and methods like getElementsByTagName(). Because these objects are live (updated immediately when the underlying document changes), they are memory intensive and can take up many CPU cycles. If you need a NodeList for only a moment, it is faster to index directly into the list. Browsers are optimized to access node lists this way. So instead of this: nl = document.getElementsByTagName("P"); for (var i = 0; i What do you say to the following performance tip from http://www.devnewz.com/devnewz-3-20030514OptimizingJavaScriptforExecutionSpeed.html ? Is he right?

NodeLists are lists of elements from object properties like .childNodes and methods like getElementsByTagName(). Because these objects are live (updated immediately when the underlying document changes), they are memory intensive and can take up many CPU cycles. If you need a NodeList for only a moment, it is faster to index directly into the list. Browsers are optimized to access node lists this way. So instead of this:

nl = document.getElementsByTagName(”P”);
for (var i = 0; i

]]> By: dave http://webkit.org/blog/13/classname-vs-style/comment-page-1/#comment-46 dave Mon, 01 Aug 2005 22:20:25 +0000 http://webkit.opendarwin.org/blog/?p=13#comment-46 Just a query about your approach to bug fixing. When you find a bug like the one you've documented, do you go looking for the same class of bug in the rest of the code (I don't mean to sound rude, just curious about the process). Just a query about your approach to bug fixing. When you find a bug like the one you’ve documented, do you go looking for the same class of bug in the rest of the code (I don’t mean to sound rude, just curious about the process).

]]>