Re:Expect Mozilla to beat IE (Score 1)

For your information, here's a comment from the main DOM engineer of Mozilla (from bug 74201 WONTFIX)

If it would've been decided in the early days of mozilla that document.all
should be supported then I wouldn've have much problem with doing so, but
deciding now to start supporting document.all is IMO a very bad idea, there are
pages our there already that use code like:

if (document.all) {
// Do IE specific stuff
} else if (document.getElementById) {
// Do mozilla specific stuff
} ...

and if we'd now all of a sudden started supporting document.all we'd break
things like this.

Even worse, the closer to IE mozilla gets (in terms of DOM functionality) the
more bugs we'll get about mozilla not working exactly as IE does, and I'm not up
for revers-engineering everything in IE at this point, that would be extremely
complicated and time consuming. We're already seeing similar problems with
mozilla's support for IE's element.offsetXXX properties, they behave more or
less the same way, but not exactly what IE does, and finding out exactly how IE
works is non-trivial (for all the hundreds of proprietary methods/properties in
IE), to say the least.

I'm all for implementing functionality in mozilla that exists in IE and is very
useful, cleanly defined and has a nice clean API, however, document.all is not
one of those things, I it's not a clean API (it's a list and a hash and callable
function, and what exactly does it contain? Who knows?), there are other nice
clean standards compliant API's that give you everything that document.all gives
you, I say that's enough.

Marking WONTFIX.