The Performance of .nodeName
I was researching various options of traversing nodes for Slick and the DOM Range for MooTools. I realized that the nodeName property is incredibly slow to access in WebKit browsers. This is because it is working with qualified names with namespaces and stuff internally.
Related Submissions:
- Enhancing Your Site with WebKit WebKit is an open source browser engine. Apple uses WebKit in Safari, Mail, and other applications. Google’s Chrome browser, along with the S60 browser and...
- 11 Ways to Increase Your jQuery Performance Optimization is something that can help the users of your application achieve actions inside of it much quicker than they may currently be able to....
- Nicer Navigation with CSS Transitions Newer versions of Apple’s Safari web browser (and Google Chrome, which is also based on Webkit) support a vendor-specific implementation of the CSS3 Transition property....
- 5 CSS Tips Every Web Developer Should Know Working with CSS can seem like a constant battle. Browsers are always changing they way they read the code (*cough* Internet Explorer *cough*), and it...
- jStorage - JavaScript Plugin to Store Data Locally jStorage is a simple wrapper plugin for Prototype, MooTools and jQuery to store data on browser side. jStorage was first developed under the name of...