MozillaZine

Mozilla 1.0 RC1 Released

Thursday April 18th, 2002

mozilla.org today released the first 1.0 Candidate, in preparation for a final 1.0 build. They'll be using RC1 to evaluate where the 1.0 branch stands as far as crash bugs, and other things that drivers@mozilla.org are tracking. RC1's changes since 0.9.9 include the abilty to view the source of a cgi (the most duped bug), reorganized context and main menus, LDAP over SSL, return recipts, new animated mail alerts on Windows, Download Manager, final xul syntax changes, and numerious other bug fixes.

You can download RC1 from mozilla.org's Releases Page or read the Release Notes. We highly encourage you to download the talkback enabled builds, so crashes can be found and logged prior to 1.0. (These pages haven't reached mozilla.org yet, you can grab builds from the FTP site.)

Once people start using RC1 and drivers@mozilla.org get a handle on how the reception of it goes, they will be deciding whether or not to release another candidate or 1.0 itself. We'll keep you updated on this process, and let you know what is decided.


#91 Re: So macpeep...

by macpeep

Saturday April 20th, 2002 12:14 AM

You are replying to this message

"Are you using RC1 full-time yet? :) If you haven't yet, then why not? You've been here for a good 2 years, and if now isn't the time, then when is? (sorry... one those "couldn't resist" type posts)"

I don't know how long I've been here really - I've followed Netscape since back in the days of 0.x versions in 1994 or whatever it was and the Mozilla project since the first day the source code was released. Been downloading nightly builds and milestones ever since they become available.

I'm not using Mozilla full-time yet.. Just some facts first: I use IE 6 for browsing and NS 4.79 for email. I would much rather just use one app for both email and browsing because for me, the typical profile of using the apps is very integrated. I might be using a bug database at work with the web browser and then send emails to someone by clicking on some mailto: link, for example. I also pretty much have both a browser and email open 24h/day so why two apps if one app solves both of those?

I'm not religious about web standards and all that part of things. I just use a web browser as an end user and as such, I don't really care too much about what standard is supported and to what extent, as long as everything *I* need it for works. The browser side of things in Mozilla is pretty much there.. There are some small glitches such as scrollbars still flashing in and out when typing in textareas every once in a while but as a whole, there's really not a lot to complain about anymore in the web browser itself. Rendering speed is good, rendering quality and correctness is good...

The email app is getting close to NS 4.7x but it's not quite there yet. There are bugs such as the "Get Msgs" button being disabled by default every time you start the Mail & News app. MAJORLY annoying. You have to click on the thread pane to activate it. The statusbar is not always updated so you don't really know if the app is still trying to create a summary file (or whatever they are called these days) or if the statusbar text just jammed at some point. There are no icons for security on the statusbar even though there are slots for it, so there are two funny looking vertical lines on the statusbar for no apparent reason. When you click on them, you get a security dialog. The history tree in the sidebar has twisties that don't react at all when you click on them. All other trees in Mozilla expand on one click on the twisties but not this tree.. Why?

These kinds of issues leads us to what I really find to be the biggest problem with Mozilla right now: UI quality. It's just not polished enough. There are way, way, way too many small inconsistencies and oddities and broken things for me to be comfortable with the application on a daily basis. Since I have absolutely no problems with IE 6 and NS 4.7x, I have no reason to switch to Mozilla until it's BETTER than those apps. I know that you can come up with a list of features in the apps and show that it has "passed" IE 6 / NS 4.7x in the features or standards race, but at the end of the day, none of that matters if the app just doesn't feel high quality and polished.

So.. you asked for a reason why I don't use it full-time yet. Well, the reason is UI quality..