MozillaZine

mozilla.org releases Mozilla Milestone 0.9.4

Friday September 14th, 2001

mozilla.org today released Mozilla Milestone 0.9.4. New to this release is the ability to disable the JavaScript window.open() method during page load and unload events. You can find more information on what's new at the release notes.

Builds are available on mozilla.org's download page(or go right to the FTP directory).

A recent post to the Mozilla builds newsgroup explains that Netscape will continue to check into the 0.9.4 branch. Work continues on the trunk toward Mozilla 0.9.5.


#159 Re: 1.0 is in

by strauss

Tuesday September 25th, 2001 9:52 AM

You are replying to this message

>> After all, Mozilla *does* support all the tags and attributes MSIE supports... by ignoring them... <<

OK, first, that's a pretty strange statement, but anyway, I'm not talking tags and attributes -- I'm talking DOM. Do you do any hard-core, GUI-application-level DHTML work? I hate to say it, I'm an old M$-hater from way back, but IE's extensions are sweet for DHTML, and the W3C stuff is totally inadequate. What is Mozilla going to give me for fine-grained control of text editing or for drag and drop between windows, for instance?

>> The moment IE wipes out any competition, there goes your companies ability to create the best application on an even playing field. <<

I don't know what you mean, or what you think that translates into in business terms. How does having to support multiple browsers help my application's competitiveness? Mostly what it does is make the test matrix twice as large, which slows down development by a factor of 50% or so due to the extra unit tests and bugs, and QA by a factor of 2 or so. Cross-platform development is hard. If the browsers have lots of obscure little bugs all over the place, it becomes _extremely_ hard, and it starts to limit the feature set to a least-common-denominator basis.

What does support for two browsers give back to us? Not freedom of choice -- we have to support every browser that our customers might use -- we have no choice.

It's really pure overhead from the developer perspective.