There has been much talk about improved CSS-support in MSIE 7, but what about
improved ECMAScript and DOM-support in MSIE 7?
Except for non Active-X XMLHttpRequest I've yet to see any explanations about
improvements in this area. Anyone who has?
I played (a small) part of reporting IE's incorrect handling of getAttribute,
setAttribute and removeAttribute on
http://en.wikipedia.org/wiki/Comparison_of_layout_engines_%28DOM%29. Naturally I
wonder: Will these methods be fixed?
Another thing I've seen is that many scripts that test for 'document.all' or
'attachEvent' or some other similar MS proprietary function often do so *before*
they test for W3C functions, as in John Resig's winning addEvent
(http://ejohn.org/projects/flexible-javascript-events/)
function addEvent( obj, type, fn ) {
if ( obj.attachEvent ) {
obj['e'+type+fn] = fn;
obj[type+fn] = function(){obj['e'+type+fn]( window.event );}
obj.attachEvent( 'on'+type, obj[type+fn] );
} else
obj.addEventListener( type, fn, false );
}
*If* MS in the future will start supporting the better function, but continues
to support their old one as well, wouldn't it be better if the checks were done
in different order?
Or to make my question really MSIE 7 specific: What will be *dropped*? What
proprietary HTML, CSS and DOM will they stop supporting, if any?
Lars Gunther
P.S. I will start using a combination of the techniques demonstrated by John
Resig and Dean Edwards (at http://dean.edwards.name/weblog/2005/12/js-tip1/) for
my own event-handling in the future.
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
