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

#188 Re: "Everything's ready but X, so we're not shippi

by NilsE

Friday June 29th, 2001 8:03 AM

You are replying to this message

>> "Everything's ready for Mozilla 1.0 but X, so we aren't shipping."

Agreed. ;-) That's what you need.

>> "Mozilla should never steal focus, all UI elements should be inside their respective windows, and the UI should not change unexpectedly (i.e things shift around) when you interact with it." would be a lot better. Right, but remember you were specifically asking not to post a "personal bug list" (tm). ;-) Anyway, in the first thread above I've been proposing a meta-bug for exactly this kind of stuff.

Basically, it appears that this discussion showed that there are quite some different views and expectations from the Mozilla project, hence the differently emphasized opinions on what the "must haves" for 1.0 are.

I basically agree with the "browser user" crowd that says:

- Now more new festures now (even when I personally really miss email encryption) - Stability is fine now, can still be improved, but no blocker anymore - Speed could be improved and footprint could be decreased, but it's about OK now and due to the x-platform development unlikely that especially speed can be improved much. Fine. - UI needs to be polished, for the various reasons that already have been noted (please note: I'm not talking about these one-pixel-off tidbits, but the annoying stuff that Gerv thankfully summarized) ;-)

So, let's go for it!


PS. Someone said this before: Gerv, thanks for asking in the first place. I do hope that the core Mozilla development team is at least now aware of our (different) views ...