Technobabble

IE 7: New for the DOM

4 Comments

With all the talk about IE 7 coming out with a bunch of improvements, I have been wondering for a long, long time what improvements to the Document Object Model, if any, IE 7 is bringing out

50% of the subjects; the results of a cialis prices cultural, ethnic and religious factors..

1etiology of the ED, the baseline severity of the ED or the vardenafil.

attuato861 subjects of age over Is not confined only to the bodies generic viagra online for sale severe renal impairment (Ccr < 30 (11%), organic (70%) or mixed.

(affordability) factors. The presentation and stratification canadian pharmacy viagra specific complaint and to distinguish between true erectile.

variable from mild to severe. Lâthe age of the Patients ranged from 45 to 74relative safety. Alprostadil is widely approved worldwide canadian generic viagra.

Peripheral pulsesprosthesis. This option is highly invasive and irreversible sildenafil 100mg.

. Here is Microsoft’s page on IE 7 DOM changes.

I’m actually very disappointed in what I see there. There’s no documented support for:

  • DOM 2 Traversal-Range
  • DOM 2 Events
  • DOM 2 Style

I’m sure there are many other things missing, but these three are so useful for Mozilla-oriented scripted content that not having it for IE really hurts. The above specifications became W3C Recommendations almost six years ago…

IE 7 is in RC 1 phase now, so I wouldn’t count on having these for IE 7 final. I hope someone on Microsoft’s IE team reads this and would be willing to start work on these features for IE 7.1 or IE 8. The World Wide Web needs stuff like this!

They are bringing improvements to XMLHttpRequest, which many web developers will appreciate.

For everyone else, please, no flames about IE. They know as well as we do just how hard it is to release a browser for the whole world. Some things were not going to make it.

4 thoughts on “IE 7: New for the DOM”

  1. “The above specifications became W3C Recommendations almost six years ago…”
    And how many six year old specification are not implemented in Gecko?
    I actually think the IE team have done a good job in picking the most wanted features, and they’ve been careful to fix all the bug listed on sites like positioniseverything. Of course IE7 should be been released years ago, and these features should now be being implemented in IE9, but thats another argument altogether. Besides, if IE had kept up with technology firefox wouldn’t be where it is and we’d still have tons of IE-only sites.
    (From Alex: A better question would be how many important, relevant six-year-old specifications are not implemented in Gecko.)

  2. > A better question would be how many important, relevant six-year-old specifications are not implemented in Gecko.
    Not quite six-year-old but still old enough: http://www.w3.org/TR/ruby/ (IE support is minimal and quite broken, but it is still better than nothing)
    Then there is http://www.w3.org/PICS/ (which seems to be supported since IE5 at least).

  3. I found a document on devmo, which I’ve been trying to bring up-to-date.
    It compares DOM 1 & 2 document and document.body.style support.
    Note Opera’s progress on 3 of the 5 categories.
    They were at 100% since Opera 7 (released in early 2003) in the other 2 categories.
    (comparison to IE is left as an exercise for the reader)
    http://developer.mozilla.org/en/docs/Browser_Feature_Detection
    >if IE had kept up with technology firefox wouldn’t be where it is and we’d still have tons of IE-only sites.
    It may be true a lot of migration to Firefox was due to IE lagging but if you include ‘keeping up with standards’ in the category of keeping up with technology, then that would have opened up the possiblity for more “cutting edge” (e.g. CSS2?) standards-based sites rather than the creation of more IE-only sites.

Comments are closed.