MozillaZine

Mozilla Adds Undetectable document.all Support, Part of New Novell Linux Distribution?

Friday July 23rd, 2004

Jacob writes: "Mozilla builds starting tomorrow will now support an undetectable version of document.all. This will help with sites that blindly use document.all in DHTML scripts. The support should also show up in the next Firefox release. More information is available in the bug."

An important thing to remember is that this will not break existing scripts that check for document.all, it will only work in cases where the script assumes it is running in IE, and does not first check to be sure that document.all works. If document.all is checked for, Mozilla will continue to block its use and act as it always has.

Update: The Register is reporting that Novell will soon be coming out with a slimmed down version of SuSE Linux targeted at exterprise desktops. The interesting part of this story is that they will be shipping a browser that "supported IE6 extensions, making it possible to access IE-only websites." Time will tell if this new support for document.all is related to the Novell news.


#19 Re: Yellow bar it?

by willll <willll@juno.com>

Friday July 23rd, 2004 4:46 PM

You are replying to this message

> Wouldn't it had been smarter to just display a small yellow bar, like it does the pup-up blocking in Fx, to say that this site uses document.all which is not a DOM supported method and that some feature will not work until the website is correctly updated?

This is the worst of both worlds: support an unstandard extension of the DOM and create more unfriendlyness towards normal users. Getting rid of unfriendness by supporting a few dynamic pages was the point of the change. Why on earth would a non-geek user care if a website used document.all without a standard alternative? They wouldn't. At all. Alerting them of it would be a waste of their time and make it seem like Firefox was a geek browser and not for them. It is a very different situation with pop-up blocking. If Firefox was a browser only for web developers, it would be a different story, but it isn't, and I'm sure this change was made to attract people who aren't web developers.

> It seems to go the wrong direction in giving a user a faulse sense of compliance.

A typical user has no sense of web standard compliance so it can't be decieved. If a web developer cares about compliance they will look at the JS console where we report this as a warning or error or something.