MozillaZine

Netscape's Plans for M14 and Beyond

Monday February 7th, 2000

Cmad writes, "Want to know more about Netscape's release plan? Another interesting article has been posted on that matter by Jim A. Roskind in the SeaMonkey newsgroup."

If the link above doesn't work for you, try this Deja.com link.

Jim goes into detail about what Netscape is expecting to do with M14 - it could turn into an alpha Netscape product, a beta product, or, worst case, they might end up holding off to M15 for a branded version. They're expecting that M16 will be feature complete (presumably the skin-switching code and security module will be in by that time, too).

Beyond the obvious performance issues, I think Netscape should really try to address the usability issues with the current skin if they are looking to push out a beta product. For example, the toolbar buttons should be labeled, and the buttons themselves should not extend over the grey space below the main toolbar -- it looks like an unintended effect (or defect).

What do you think? Post your thoughts and ideas in the forum for this news item, but since this has been a contentious issue in the past, I'm asking that you please keep your post civil.

--MozineAdmin


#28 They are useful, but here's what you need to do...

by mozineAdmin

Monday February 7th, 2000 5:55 PM

You are replying to this message

Search for bugs that address these issues, and if you don't find them, file them. That's the way that they can be addressed (assuming that you are not a coder). You make a number of good points, many of which I know are addressed by already-filed bugs.

The current UI, in all its non-complete glory, is not indicative of how the final UI will end up. The fact of the matter is that every Mozilla developer you may talk to will state that there is still *much* work to be done on the UI front, but there are much more important tasks that need to be dealt with *now*. That does not mean, however, that you should not file bugs against all usability issues you see. Just be sure to check for dupes first.

I must state, however, that these issues do not, in *any* way, "reveal a core problem with usability and appearance review on the Mozilla project". When the UI is at a state where the developers are actually stating "this is done", that's when you should worry. They are keenly aware that there are many many loose threads on the UI at this point. They will address them.

Well written bug reports help a lot. Please consider submitting them. Please be sure, however, to file bugs separately (don't list all of your issues in one big bug). If you do, the bug will probably be marked invalid for lack of specificity (but they'll probably contact you first).

The Bugzilla Helper recently created by Christine Begle is an easy way to get started filing bugs with BugZilla. The URL for it is below.

<http://www.mozilla.org/quality/help/bug-form.html>