getElementsByClassName re-re-re-visited
There have been numerous attempts at creating the most optimal getElementsByClassName implementation. I also took a shot at it back in 2005 and back then Opera had some performance problems with getElementsByTagName, IE's implementation of nodeList.item() proved to be a major hog and Firefox' XPath implementation was far from perfect. Eventually I came up with a hybrid solution that combined the fastest approaches for each tested browser (with IE being declared the winner on performance).
Read more »
Read more »
prototype: IE and the cost of Element.extend()
It seems that prototype like YUI is more and more moving towards code purity and are neglecting performance. I noticed this recently when I was benchmarking my own getElementsByClassName function and comparing it to the established javascript libraries that also support this functionality.
Read more »
Read more »
HTML5 - why not use XML syntax?
The XML-fanboys are at it again, this time tripping over the actual syntax used in W3C documents such as the HTML 5 differences from HTML 4 doc. Next comes a flurry of mails from people suggesting that HTML5 should actually make XML-syntax an author-conformance requirement.
Read more »
Read more »
Fixing the web? Fix your browser!
HTML5: Microsoft and the opt-in catch
It's been a busy month sofar on the public-html mailing list. Microsoft has joined the working group and Chris Wilson put on his chair hat (but is still mostly wearing his Microsoft hat) and WA1.0 (aka HTML5) has been offically proposed as a starting point for the new HTML specification.
Read more »
Read more »