MozillaZine

Firefox Pre-Preview Release Available for Testing

Saturday September 11th, 2004

Asa Dotzler writes "We took one more important change into the builds last night, moving from a blacklist to a whitelist for external protocol handlers, so today's builds are the new candidate 1.0PR builds. If all goes well with these builds, they'll become the official Firefox 1.0 Preview Release builds on Tuesday morning. Please help us test these bits and if you find any major regressions, please file bugs and nominate those as PR blockers with the bug flag "blocking-aviary1.0PR?" so that the Aviary team will see.

Download the 0.10 (1.0PR) candidate builds now: Windows installer Linux installer Mac disk image (Other formats can be found here.)

Note that this is not the final 1.0 Preview Release. That will happen on Tuesday if all goes well with the testing of these candidate builds. We appreciate any and all help testing the candidates and strongly encourage you to report any problems. Only you can prevent buggy releases ;-)"


#73 Most crucial usability bugs

by johann_p

Monday September 13th, 2004 2:20 AM

You are replying to this message

Out of my head, here are the usability bugs that I think are most crucial - and most embarrassing when not solved in 1.0:

Improve the dialog(messages) shown when a user starts a second instance of FF. Right now, the dialog does not tell that another instance is already running and simply shows the "pick profile" list - often with a single profile. Only when the user picks that profile will he see a message that it is in use.

If an URL is loaded in the background and there is a connection problem, the URL is not shown in the URL entry field and not in the history. Retrying is impossible and this often means that the URL is lost.

As stated above, the default setting for downloads should be "ask" not "Desktop", expecially not on Linux.

The "new tab" icon should be standard - it was idiotic to remove it and force users to install an extension for it.

Tabs should either be scrollable or wrap to a new line if there are too many to fit in a row - currently, tabs simply disappear and are unaccessible.