MozillaZine

Full Article Attached Towards Mozilla 1.0

Tuesday June 26th, 2001

Gervase Markham recently posted his feelings on what a 1.0 release of Mozilla would be. Gerv has sent us the follow-up to that posting, including much of the feedback he received. To read it, click the full article link. Once you have read through it, we welcome you to post your feelings on what you think a 1.0 release would have. [As Gerv says, please don't post your favorite list of bugs, only the criteria for choosing what bugs to fix.]


#155 Functionality, Stability, Polish, Performance...

by schapel

Thursday June 28th, 2001 2:36 PM

You are replying to this message

...these are the qualities I'd like to see in Mozilla 1.0.

First and foremost, I use Mozilla to get work done. The worst bugs are those that cause functionality to be missing. I don't mean missing features like full screen... I mean that sometimes Mozilla cannot download a file that I need. In these cases, I have no choice but to use another browser. The cases where Mozilla cannot perform a common function that other browsers can perform should be given top priority for Mozilla 1.0.

Closely related to functionality is stability. The more Mozilla crashes, the harder it is to get work done. Top crashes and dataloss crashes should get priority right behind functionality issues.

If Mozilla is able to perform the tasks I need it to without crashing, I'm relatively happy. However, I start getting picky about UI issues. My latest beef is that nearly every time I download a file I must set the default to "Save to disk". This is quite annoying, so these UI polish issues should be given priority right behind crashes.

I know that many people would like Mozilla to run faster, but with faster computers becoming available all the time, this will become less of an issue. I have an 800 MHz Pentium III with 256 MB RAM and Mozilla does not seem any slower than IE 6. Besides, given the choice of Mozilla not working, crashing, being positively irritating, or just being a little slow, I choose slow any day. Performance issues should come behind functionality, stability, and polish.

Addtional features that are not needed, enhancements, and theoretical targets like 100% standard compliance should wait until these more pragmatic issues are solved. I'm more interested in getting Mozilla to the point that it can perform all the tasks I need without crashing, being irritating, or being slow than I am about some arbitrary goal like the GNKSA.