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

#186 Re: Re: "Everything's ready but X, so we're not sh

by _Lewellyn

Friday June 29th, 2001 7:42 AM

You are replying to this message

I don't know what platform you use, but I'm willing to make a guess it's not Mac. Before you say "Reassign most of the developers working on the browser", be sure that you just aren't lucky. ;) The past few months my Windows machine hasn't been booting windows (Been using Arachne for DOS <> for various reasons...), so I've been testing nightlies on MacOS. They're coming along, but the UI needs work. I've noted a bug in particular earlier, so I won't note any more particular bugs. I also am not sure if you can even *use* certain features on the Mac yet.

A short list of things I'd like fixed on the MacOS at least. (For an idea of the types of UI/performance bugs I've seen...)

#1: Blank windows are bad, as I've said before. At least load the chrome. Mac users are not going to uninstall ATM in order to run Mozilla.

#2: The Preferences window. (Where to begin?) 2a: the left pane should scroll. 2b: the right pane should: scroll, resize window when content exceeds space [not necessarily possible on say 640x480 or 800x600], or be resizable by user. 2c: should be resizable by user. I'll stop there on Preferences...

#3: There should be an easy way to turn off search from address bar. There may well be, but the preferences window is blank. no chrome even... ;) (see #1)

#4: Is there -turbo on a Mac? If so, where is it documented? If not, why not? Simply because of the Application Switcher?

#5: Mozilla should *NOT* need its memory partition resized to 64MB to view some web pages.

#6: Scrolling past the end of a textarea with the right arrow key should not take me back to the top.

Those are the types of things a user will definitely notice in a 1.0 release. It's things like this that should stop a 1.0. If it glares at you, don't put on sunglasses.

Also, a good idea of what users see is at <…6204.ur.10201-601-6266204> . Note the "Stability" indicator...