Posted by Daniel Thu, 02 Feb 2006 01:37:52 GMT

How IE7 Can Avoid Irrelevance:

At a minimum, dynamic web apps need the following out of IE and JScript in the very near future:

  • Memory leaks need to simply disappear
  • Fix the cache+gzip bugs
  • Give us getters/setters in JScript or give back watch()
  • Fix the event object. Pass it in to DOM handlers by default. Also, offsetLeft and offsetTop are so ambiguious as to be useless. Give us currentTarget.
  • Bump the limit on the number of concurrent HTTP connections if those connections are initiated after onload (either via XMLHTTP or other methods)
  • Today, allocating more than 5K objects or so brings JScript to its knees. Object allocation cost needs to be O(1)
  • Either revive (and start to fix) VML or give it an SVG-Tiny+DOM facade
  • Give us a persistent, string-keyed, local cache in the MB range (5-10MB/domain seems a good start)
  • Fast DOM queries. CSS selectors or XPath, we don’t care. Just give us a way to say “get us all DOM node objects matching this”
  • A way to toggle the box model on a per-element basis without switching doctypes. The CSS 3 box model spec seems a good starting point

If Microsoft is to re-build any credibility around their browser, they need to show us the goods. CSS fixes won’t suffice this time around.

[No surprise that this list is to the point.]
Source: Continuing Intermittent Incoherency