Mozilla 0.9.8 Released

Monday February 4th, 2002 today released Milestone 0.9.8 of Mozilla. This release includes the new OS rendered classic theme on Mac OS X and Windows XP, a partial rewrite of the addressbook adding a quicksearch and additional printing enhancements, support for MNG animations, DOM Inspector on the Mac, dynamic theme switching, inline CSS support in composer, and so much more. You can check out the release notes for more information on what's changed and other issues.

Builds are available on's releases page, or on the FTP Server.

With 0.9.8 released, attention turns to 0.9.9, which many believe to be the last milestone prior to 1.0.

#136 Re: Re: Re: javascript

by fuzzygorilla

Thursday February 7th, 2002 11:55 AM

You are replying to this message

Thank you for posting the links you were seeing problems with. I am *NOT* a javascript programmer, but I took a quick look at the souce and Bugzilla. The first problem you found (<>) is a problem with the JS on the website. A Bugzilla Evangelism bug exists - Bug 120710 <> . The second problem you found (<>) also appears to be a JS problem with the website. The pictures below the -ve- headline are part of a table that is shown only if (navigator.appName.indexOf("Netscape") == -1) - which means you won't see it in Mozilla (hte indexOf is 0 in Mozilla). There is no Evangelism bug on this but the issue is the JS on the website, not Mozilla. The third problem you found (<>) I have not been able to see. I am not seeing a context menu in IE6. The site looks identical in IE6 and Mozilla. I am probably missing something obvious :-) The fourth problem you found (<>) I also see. Looking at the JS code, I don't see the obvious flaw of voodooextreme - it looks like the authors will try not to use the IE DOM "document.all" with Mozilla. Since I don't do JS, there is not much more I can say. I checked the JavaScript Console and there was one error recorded ( Error: company has no properties Line:19). I would suggest you open up a bug in Bugzilla. At worst they turn it into an Evangelism bug and contact the website. The fifth problem you found (<>) I also see. Unfortunately, it is also beyond my meager (non-existent) abilities. I would suggest another bug.