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.]


#77 Cut the bull or put the bull in?

by jelwell

Wednesday June 27th, 2001 2:19 PM

You are replying to this message

For starters, I don't see any vagueness when I say "Make it as fast and small as IE 5.5 - both for page loading time and for startup time". Anyone think that can't be checked off a list?

I think a lot of the goals outlined here are rediculous. So I've put together a new list. I'm calling it:

Joe's list of I hope they don't listen to Gerv for 1.0.

1. use voting - I hope that voting doesn't come into the checklist at all. I see no reason to treat voting as anything different than what it's meant in the past releases.

2. don't set a performance goal - this goes against the number 1 complaint against using Mozilla; so, you better set a performance goal, and you better try to hit it.

3. CSS-isation of Composer - I've been told this means changing html bold elements into something like div's with style=bold. Won't this just make the HTML output less readable on older browsers? Can't we give composer something better to shoot for?

4. Good Net-Keeping Software Award. - raise your hand if you think consumers care. while your at it raise your hand if you think mozilla 1.0 is for developers rather than users. ;) Again, I think we can come up with a checklist for mail that people really care about. If we're going to add more features into Mail (as achieving this award would require) why don't we try to implement something useful like system tray biff notification?

5. Full standards support. - This is a hard one. But, seeing how there is soo much more to work on; I'd have to say that "most standards support" should be good enough. As long as we support more than the competition, and we don't have any broken standards support (we don't want people's web page code to break when we fix our bugs) - then we should be ok.

6. Build system cleanup. - you can already selectively build individual components. Anyone think that we'll win more than 2% of the market with this one? :P

I'm harsh. I know. I can count two goals that Mozilla 1.0 should shoot for. They're very simple. 1. Forwards Compatibility. - After moz 1.0 is released, future versions of mozilla should be ready to be 100% backwards compatible with previous releases, including 1.0. This means API freezes. This means cutting any API support (including, but not limited to DOM, HTML, Javascript, XUL)that is broken, that you're planning on fixing. I shake when I say "Fix the Theme support, or cut it". But we all know that in it's current form Themes don't work between releases. Theme Developers have to reimplement themes for every release.

2. Make it as fast and small as IE 5.5 - both for page loading time and for startup time. Does this sound vague to anyone? If it's vague I'll gladly point you to charts that are sent out regularly within my company that address Mozilla's speed on a week by week basis, as compared to IE.

Joseph Elwell.