Advertise on MozillaQuest Magazine Getting Started with Wireless Network Technology MozillaQuest MQ Logo
MozillaQuest the on-line computer magazine
July 2, 2003
About Computers On-Line

TotalShells.com

EPIX Internet Services
MozillaQuest Magazine Front Page button

Internet & Web browsers button

custom Netscape & Mozilla themes & skins button

Digital Photography

Graphics

IRC - Internet Relay Chat - Chat button

Linux buttonLinux for Windows Users

Mozilla button

Multimedia

Netscape button
network articles

tutorial - help - how to button

Web Page Design

Web Tools

Windows button
..

MozillaQuest Magazine has the best, most balanced, accurate, robust and in-depth coverage of AOL-Netscape's Mozilla 1.0 browser on the Internet. I'ts all on MozillaQuest Magazine.

Mozilla 1.4 Browser-Suite -- AKA Netscape 7.1


Mike Angelo -- 1 July 2003 (c) (Revised 2 July 2003)


Mozilla 1.0 Coverage



AOL-Netscape's Mozilla Organization placed its Mozilla 1.4 browser suite on its public FTP server 30 June 2003. The Mozilla 1.4 release is nearly seven weeks behind its scheduled 21 May 2003 release date.

Its predecessor, Mozilla 1.3 was released nearly sixteen weeks ago on 13 March 2003. In effect, Mozilla 1.4 will be a replacement for Mozilla 1.3.

The Mozilla 1.4 download information and links are at the end of this article. What's new in Mozilla 1.4 is further down in this article.

One factor that likely played a substantial role in the nearly seven-weeks-late release of Mozilla 1.4 is the mounting bugginess of the Mozilla browser suite. On Mozilla 1.4 release day, there were some 31,300 open/un-fixed new, assigned, and reopened bugs in Bugzilla, the Mozilla project bug-tracking database. More about that further on in the article.

Another factor that likely played into the seven-weeks-late release of Mozilla 1.4 is what appears to be less coding-support from the Mozilla Organization's de facto parent company, AOL-Netscape.

A third factor is loss of focus, which is nothing new in Lizard Land. Mozilla development is shifting from the current Mozilla browser-suite development to a collection of independent Internet-related applications; (1) Phoenix, a stand-alone Web browser, (2) Minotaur/Thunder-bird, a stand alone e-mail and news client, and (3) Gecko, the layout engine that underlies the Mozilla Web-browser suite, Phoenix, and Minotaur -- plus XUL and the Mozilla Applications Programming Framework (APF).

For more information about the decreased coder-support from AOL and the diverging focus problems, please see our article, Major Morphing in Mozilla Project Organization and Objectives Proposed -- Part 1: Mozilla Management Reorganization and Splitting the Browser-Suite into Stand-Alone Products.

AOL-Netscape's Mozilla Organization placed Mozilla 1.1, the first .x upgrade to its Mozilla 1.0 browser-suite on its public FTP server on 26 August 2002. Mozilla 1.0 was released 5 June 2002.

Mozilla or Netscape Edition Release Date
Moz 1.0 5 Jun 02
NS 4.8 23 Aug 02
Moz 1.1 26 Aug 02
NS 7.0 29 Aug 02
Moz 1.0.1 11 Sep 02
Moz 1.2 26 Nov 02
Moz 1.2.1 02 Dec 02
NS 7.0.1 10 Dec 02
Moz 1.0.2 13 Dec 02
Moz 1.3b 10 Feb 03
NS 7.0.2 18 Feb 03
Moz 1.3 13 Mar 03
Moz 1.4a 1 Apr 03
Moz 1.4b 7 May 03
Moz 1.4 30 Jun 03
NS 7.1 30 Jun 03
Table 1. Major Mozilla and Netscape releases from Mozilla 1.0 to present.

Each new Mozilla release has new and improved features. However, Mozilla has been and still is plagued by lots of bugs. Please see Figures 1 and 2.

Figure 1. Increases in open, un-fixed, un-resovled bugs listed in Bugzilla, the Mozilla Project bug-tracking database, from October 2001 to 30 June 2003. Please see Table 1, above, for the data points.

For discussion about what bug counts mean and how to intrepret them, please see the section Bug Counts Reflect the Overall Product Quality in our article A Quick Look at Some Mozilla 1.0 Browser-Suite Annoyances, Bugs, And Issues. For more information about Mozilla preformance problems please see our article Mozilla 1.0 Browser-Suite Performance -- Speed, Stability, and Memory Hogging

Please see Table 2, below, for the increase in Mozilla bugginess from the Mozilla 1.1 release to the Mozilla 1.2 release. Table 3, below shows the increase of bugs from Mozilla 1.2 to 1.3.

Figure 2. Increases in open, un-fixed, un-resovled bugs listed in Bugzilla, the Mozilla Project bug-tracking database, from Mozilla 1.1 (26 August 2002) to Mozilla 1.4 (30 June 2003). Please notice that while targeted bug counts have gone down by 807 bug reports, un-triaged bug counts have increased by 3,559 bug reports, and the open, un-fixed, un-resovled bugs has gone up by 4,417 bug reports. This suggets that Mozilla bug triaging is getting very far behind and bugs are not even being assigned to bug fixers.

For discussion about what bug counts mean and how to intrepret them, please see the section Bug Counts Reflect the Overall Product Quality in our article A Quick Look at Some Mozilla 1.0 Browser-Suite Annoyances, Bugs, And Issues. For more information about Mozilla preformance problems please see our article Mozilla 1.0 Browser-Suite Performance -- Speed, Stability, and Memory Hogging

For the details and more information about the problems and bugs that forced the Mozilla Organization to recall Mozilla 1.2, please see our article, Buggy Mozilla 1.2 Recalled.

However, not all the bugs that were targeted to be fixed before the Mozilla 1.4 release have been fixed or resolved. A check of Bugzilla, the Mozilla Project bug tracking database on Mozilla 1.4 release day showed that there were more than 2,500 (2,531) unfixed and unresolved bugs targeted to have been fixed or resolved before the Mozilla 1.4 release. Of that more than 2,500 bugs, 2,159 were targeted to have been fixed or resolved before release of Mozilla 1.4a.

Mozilla 1.3 was about three weeks late because of unfixed bug problems. Mozilla 1.3b was late, also. The Mozilla Roadmap called for Mozilla 1.3b to have been released on 24 January 2003. Unfixed bugs caused Mozilla 1.3b to be released 10 February 2003, nearly three weeks late.

The Mozilla 1.3a release was a week late. The Mozilla Roadmap called for Mozilla 1.3a to have been released on 6 December 2002. However, unfixed bugs prevented Mozilla 1.3a's timely release, too.

In many ways the Mozilla browser-suite is a very nice product. It has lots of interesting and handy features. A major problem, however, is that the Mozilla developers throw features into their Mozilla browser-suite without getting rid of the bugs in the new features. It seems to be that same childish attitude that comes to the front in Learning from Mozilla's mistakes, by Robin "Roblimo" Miller on NewsForge.com.

Mozilla 1.4 Kills Mozilla 1.0, Etc.

The releases of Mozilla 1.4 puts final nail in the coffin of the Mozilla 1.0 browser-suite and its ensuing 1.0.x editions. It now officially replaces Mozilla 1.0.x as the stable, long-lived, Mozilla branch. However, we heard that long-lived branch plan before.

Despite past plans to have Mozilla 1.0 serve as a long-lived branch, we suspect effectively killing Mozilla 1.0 as soon as it could be killed had been the intent of the Mozilla Organization all along -- despite Mozilla Organization verbiage that Mozilla 1.0.x was supposed to be a long-lived branch. However, that is another story for another day. Meanwhile, please see the sidebar About the Mozilla Organization Verbiage to your right. Will Mozilla 1.4 suffer the same fate?

On the other hand, AOL-Time-Warner continued to base its Netscape 7 releases on Mozilla 1.0.x code. Netscape 7.01 was based on pre-Mozilla-1.0.2 code. Netscape 7.02 was based on Mozilla 1.0.2 code. Incidentally, Mozilla 1.0.2 was released on 15 January 2003. However, Netscape 7.1 finally moves up to current (Mozilla 1.4) code.

About the Mozilla Organization Verbiage

On 16 October 2001, the Mozilla Organization's CTO, Brendan Eich, promulgated his Mozilla 1.0 Manifesto as an adjunct to the October 2001 Mozilla Roadmap revisions. In that Manifesto, Eich decreed that (a) Mozilla 1.0 and its 1.0.x progeny would have at least a one-year life-span, (b) that the Mozilla 1.0 release would be of high quality, (c) that Mozilla Organization's reputation was at stake, and (d) that Mozilla 1.0 was to be finished and released within six months, to-wit, April 2002. The16 October 2001 Roadmap Schedule set the Mozilla 1.0 release for 5 April 2002. That did not happen.

The Mozilla Organization has failed to successfully implement Eich's Manifesto on all four counts:

(a) With the release of Mozilla 1.1, the Mozilla Organization has effectively killed the Mozilla 1.0.x branch in a little more than two months after its release rather than keeping it viable for the minimum one year called for in Eich's Manifesto.

(b) Mozilla 1.0 is froth with performance problems, bugs, annoyances, and all sorts of issues. We have documented that throughout our comprehensive Mozilla 1.0 coverage. The infamous Oingo.com bugs alone are enough to take Mozilla 1.0 out of the high quality category. Lack of a spell checker for the E-mail, News, and Composer modules is enough to take Mozilla 1.0 out of the high quality category. And so forth!

(c) As stated in (b), immediately above, Mozilla 1.0 was far below a high quality release. Although Mozilla 1.0 has lots of nice features and is a usable product, it also sucks in many ways too. To the extent that the Mozilla Organization's reputation depended on Mozilla 1.0, the Mozilla Organization has earned itself a lousy reputation -- primarily among those who do not base their evaluations of products and producers on emotion, fanaticism, unsubstantiated or misleading claims by a product's evangelists, or just merely hatred of Microsoft, and so forth.

Face it, if Mozilla had a good reputation and were a high quality product, it would have more than less than 1% of the browser market.

(d) Mozilla 1.0 was released on 5 June 2002, two months past Eich's six-month deadline which expired in April 2002.

Overall, Eich's Manifesto is a fair plan, horribly executed.


From Eich's Manifesto:

Mozilla 1.0" would be: . . . * The first major-revision-number milestone release (mozilla1.0) of the Mozilla browser application suite and platform from mozilla.org. A release of higher quality than any delivered so far, on whose quality our reputation is at stake precisely because 1.0 is such a coveted and feared version number. . . . * A stable, long-lived branch . . . (a year minimum, at a guess) . . .

The majority of staff and drivers surveyed believes that the "1.0" brand should be used sooner rather than later to identify our stable, long-lived branch with API commitments. We believe "sooner" means within the next six months, based on feedback from various vendors, book authors, and others in need of such a branch."

mozilla 1.0 manifesto, Brendan Eich, The Mozilla Organization (February 8, 2002 revision).

AOl's Mozilla Note:

Some of the Mozilla fans insist that Mozilla is not AOL-Netscape's Mozilla. We do not buy into that malarkey. To see why we do not buy that Mozilla-fanatic malarkey, please check our article Is Mozilla Actually AOL-Netscape's Mozilla?

That article, of course, is just a little over a year old now. Since that article was published, there has been some attempt by the Mozilla people to make it appear that Mozilla is not AOL-Netscape's Mozilla. Moreover there has been some scuttlebutt that AOL has pulled some of it developers off the Mozilla Project.

Nevertheless, we still believe that for all intents and purposes, Mozilla is AOL-Netscape's Mozilla. The lion's share of Mozilla code and Mozilla bugs were provided by paid AOL-Netscape employees, plus some paid employees of other companies involved with the Mozilla Project in a very minor way. Certainly, lots of independant/volunteer people contributed code to Mozilla too. Nevertheless, Mozilla still is primarily and AOL-Netscape operation.

See for example Mozilla Bug 192294 hangs at various URLs (Windows 9x-specific). The bug reported stated: Using Mozilla 1.3 series 2003020708 on Windows 98, Slate now causes Mozilla to hang. Seems to happen each time. I go there, open 5-6 tabs. Start reading each one, closing the tabs after I finish reading them. Pretty soon, Mozilla stops responding and hangs. Mozilla can then be killed with Ctrl-Alt-Del. . . This is a recent regression.

This Bug 192294 was opened on 7 February 2002 and marked as critical and targeted to Mozilla 1.3b. In Comment #2, the bug reporter suggest this bug should be a blocker for Mozilla 1.3. However, Mozilla 1.3b was released with this critical bug not fixed. According to the Mozilla 1.3b Release Notes: * Windows 98 users are experiencing regular application hangs. This doesn't appear to impact NT,2K or XP. (bug 192294).

This bug was marked fixed on 12 February 2003 at comment #62.

There is a link to this bug in the Resources section at the end of this article.

It has been more than a year since the release of Mozilla 1.0. However, rather than use that year to get rid of Mozilla bugs and problems, the Mozilla developers have added lots of features. Features are nice, but bugs are not nice.

The result is that on balance and simply put Mozilla 1.2 and 1.3a were crap! They were chock full of bugs. Mozilla 1.3a was slower than molasses unless you have a high speed computer with lots of RAM. This is particularly noticeable on Windows 9.x machines, which do not handle memory hogging and other such resource mismanagement problems as well as Linux, or even Windows 2000-based boxes.

We have not finished testing Mozilla 1.4 yet. However, AOL-Netscape's Lizard does not seem to be one that can change its spots. While the Mozilla 1.4 AOL-Netscape Lizard will have more features than do Mozilla 1.2.1 and Mozilla 1.3, it likely will come with most all of those bugs, resource hogging, and poor performance spots in Mozilla 1.2.1 and Mozilla 1.3.

Mozilla 1.1 brought down one of our Linux test machines. It is a 1-GHz Pentium 3 with 512-MB of hard RAM and 512-MB of Linux Swap space on the hard drive, running Mandrake 9.0. Mozilla sucked-up some 84.8% of memory -- pulling the free Swap space down to 14-KB, which resulted in the box locking.

The memory-related stats for mozilla.bin from the Linux TOP utility observed when this Linux lock-up occurred include a SIZE of 788-MB and an RSS of 413-MB. The Manual page for TOP describes SIZE as the size of the task's code plus data plus stack space and RSS as the total amount of physical memory used by the task. At the time of the lock up on the Mandrake 9.0 box there were 133 processes -- 106 sleeping and 27 running.

Of course allotting more Linux Swap space might prevent Mozilla from locking the box. However, there is no reason a well-designed and well-programmed Web browser should eat up 84% of memory on a box with 512-MB of hard RAM. In other words, Mozilla is a poorly-designed and poorly-programmed application.

Much as with the pretty yet sour lemon, the Mozilla 1.x branch (as opposed to 1.0.x branch) was loaded with new features (the pretty part) but also had lots of obnoxious bugs (the sour part). Mozilla 1.2 was so bad that it had to be recalled and replaced with Mozilla 1.2.1.

Mozilla 1.2a was released with nearly 1,300 bugs still targeted just to it. And that's just a smattering compared to the 27,435 open new, assigned, and reopened bugs listed in Bugzilla, the Mozilla bug-tracking database at the time Mozilla 1.2a was released -- plus 4,584 unconfirmed bugs. The unconfirmed bug count was up to 7,583 on Mozilla 1.4 release day.

On the day Mozilla 1.2.1 was released there were more than 29,000 open new, assigned, and reopened bugs listed in Bugzilla plus more than 5,300 unconfirmed (not yet triaged) bugs listed in Mozilla's Bugzilla. Interestingly, nearly 3,000 of those 29,000 bugs were targeted to have been fixed before release of Mozilla 1.2. Even more interesting is that only 28 of those then yet unfixed 3000 bugs were targeted for Mozilla 1.2. All the rest of those nearly 3,000 bugs were supposed to have been fixed before release of pre-Mozilla-1.2 milestones -- and they should have been fixed long before release of Mozilla 1.2.

On the day Mozilla 1.3b was released, there were more than 30,244 open new, assigned, and reopened bugs listed in Bugzilla plus nearly 5,700 unconfirmed (not yet triaged) bugs listed in Mozilla's Bugzilla.

When Mozilla 1.3 was released, there were more than 30,500 open new, assigned, and reopened bugs listed in Bugzilla plus more than 5,900 unconfirmed (not yet triaged) bugs listed in Mozilla's Bugzilla.

On Mozilla 1.4 release day, there were more than 31,300 open new, assigned, and reopened bugs listed in Bugzilla plus more than 7,500 unconfirmed (not yet triaged) bugs listed in Mozilla's Bugzilla.

The problem, is that the Mozilla project mangers are unable or unwilling to bring Mozilla development builds within quality control parameters within project release-time schedules. And that happens in part because the Mozilla code-base has become too darn clumsy and too darn buggy.

The points here are simple ones. The Mozilla developers are not getting bugs fixed on schedule. Bug counts are increasing. New code, such as new features and improvements, is being written to an increasingly buggy code base -- thus compounding the bug problems. Mozilla is a poorly managed project! Please see Tables 2 and 3, below.

Too Many Crash Bugs in Mozilla 1.4

At the time Mozilla 1.0-RC1 was released there were 533 "crash" bugs listed in Mozilla's Bugzilla bug-tracking database and there were 561 "crash" bugs listed when Mozilla 1.0-RC2 was released. The "crash" bugs count was up to 618 open crash bugs by the time Mozilla 1.1a was released and the "crash" bugs count was 620 open crash bugs when Mozilla 1.1b was released. On Mozilla 1.1 release day, the "crash" bugs count was 663 open crash bugs. By the time Mozilla 1.2.1 rolled around, the "crash" bugs count was up to 718 open crash bugs.

On the day Mozilla 1.3b was released, the "crash" bugs count was down to 672 open crash bugs. When Mozilla 1.3 was released, the "crash" bugs count was down to 665 open crash bugs. Now, on Mozilla 1.4 release day the count is up to 704 "crash" bugs. That is too darn many crash bugs.

Mozilla Not for End Users

Apparently, the Mozilla Organization does not desire to attract end-users to the Mozilla browser suite. Interestingly, the official position of AOL-Netscape's Mozilla Organization is that it does not want end-users to run the Mozilla browser suite.

Interestingly, since we raised the "end users" issue in previous articles, there appears to be a movement afoot by some people in the Mozilla Community to get-real and make Mozilla 1.0, et sequitur, an end-user product. That's a good move!

If you are an end-user that would like to discuss Mozilla or would like some Mozilla help, try the #ChatZilla, #Mozilla, and #Netscape channels on the EFNet IRC network.

These IRC channels are not affiliated with AOL or its Netscape and Mozilla divisions. It's mostly Mozilla and Netscape users helping other Mozilla and Netscape users. You also will find #Caldera, #KDE, #Linux, #Mandrake, #RedHat, #SuSE, and #Windows channels on EFNet too.

Incidentally, ChatZilla is an IRC client that comes with Mozilla. Give it a try. To launch ChatZilla just go to the Mozilla Menu Bar and click Window > IRC Chat.

For more information about Mozilla 1.0, please see our Mozilla 1.0 comprehensive coverage articles:

What's New in Mozilla 1.4.

Here is what is new in Mozilla 1.4 according to the Mozilla 1.4 Release Notes:

New Features and Fixes

* Mozilla on Windows now has support for NTLM authentication. This enables Mozilla to talk to MS web and proxy servers that are configured to use "windows integrated security".

* Mozilla's bookmarks have been overhauled. Bookmarks now include a root level folder, the ability to have two differently named bookmarks pointing at the same location, site icons in the Bookmark Manager and Bookmarks Sidebar, and separators now have support for labels.

* Composer now supports click and drag dynamic image and table resizing. If an image is selected or if the caret is placed inside a table, eight resizing handles appear and allow to resize the image/table with a simple click/drag/release. In the case of an image, the resizing is done real-time and a semi-opaque shadow of the image at its target size is shown during resizing. A tooltip shows in real-time the target size in pixels, and the relative change in pixels too.

* Mail now has junk-mail context menu items, a "delete junk mail" menu item and many other usability improvements for junk-mail controls.

* Pop-up blocking has been streamlined to improve usability.

* Users can now specify "blank page," "home page," or "Last page visited" for each of first window, new window and new tab.

* Users can now specify default font, size and color for HTML mail compose.

* Image blocking/disabling is now more flexible and users can "view image" to see blocked or not loaded images.

* "Launch file" after downloading has been enabled for .exe files

* It is possible to build Mozilla for Win32 using GCC. See the win32 build instructions for details.

* Proxy auto-config (PAC) failover has been implemented

* Mozilla 1.4 contains thousands of additional bugfixes, including changes to improve performance, stability, web site compatability, standards support, and usability.

New Issues

These are items that have been added to the known issues page since the last milestone although the bugs themselves may have existed previously.

* The Linux binaries distributed by mozilla.org are now compiled with GCC 3.2. If you're using these binaries then you will need the 3.2 version of the Java Plugin from Sun J2SE v 1.4.2 (or the Blackdown JDK 1.4.1 compiled with GCC 3.2.) The Sun Java Plugin is compatible with modern Linux versions like Red Hat 8 or later and SuSE 8.1 or later (the plugin depends on a newer version of libgcc_s.so, installing the GCC supplements for Red Hat 7.3 -GCC 3.1 Compiler Suite for Red Hat Linux 7.3 - may allow for some older Red Hat Linux to run the plugin) Users of older Linux versions should either install the egcs 1.1.2 build of Mozilla and the JRE 1.4.1 or wait for a Mozilla version compiled specifically for their Linux distribution.

* If you're using the Linux GCC 3.2 binaries compiled by mozilla.org then JavaScript access to Flash will not work.

* If you are experiencing crashes on startup in xpcom.dll it is very likely that there is an incompatibility with some third-party extension. To work around this problem, uninstall your previous version of Mozilla, and completely delete the Mozilla install directory before performing the new install. You will not lose your profile data (such as bookmarks, preferences and cookies) but any third party extensions and plugins may be lost.

The download information and links are in the Resources section at the end of this article.

Lots of Bugs for Mozilla 1.1, 1.2/1.2.1, and 1.3 -- More for 1.4

We addressed some concerns about Mozilla's runaway bugs problems in our article, Mozilla Milestone 0.9.9 Branched Behind Schedule. In that article, we noted that on 1 March, there were some 12,137 targeted new, assigned, and reopened Mozilla bugs and 21,199 new, assigned, and reopened bugs (open/unfixed bugs) altogether.

On May 10, when Mozilla 1.0-RC2 was released, there were 12,417 targeted, new, assigned, and reopened Mozilla bugs and 23,569 new, assigned, and reopened bugs (open/unfixed bugs) altogether. Mozilla 1.0-RC2 had more bugs than did Mozilla 0.9.9.

On Mozilla 1.1a release day, there were 1158 bugs targeted to Mozilla 1.1a, 12,638 targeted, new, assigned, and reopened Mozilla bugs, and 24,850 new, assigned, and reopened bugs (open/unfixed bugs) altogether. Mozilla 1.1-alpha had more bugs than did Mozilla 0.9.9.

By the time Mozilla 1.1-beta was released, the targeted, new, assigned, and reopened Mozilla bugs count was down to 12,462. However, new, assigned, and reopened bugs (open/unfixed bugs) altogether bug count was up to 25,939 bugs.

On Mozilla 1.1 release day, the targeted, new, assigned, and reopened Mozilla bugs count was 12,301. New, assigned, and reopened bugs (open/unfixed bugs) altogether bug count was up to 26,856 bugs. In addition there were 4,161 un-triaged (unconfirmed) bugs listed in Bugzilla then.

By Mozilla 1.2 release day, the targeted, new, assigned, and reopened Mozilla bugs count was up to 12,512. The new, assigned, and reopened bugs (open/unfixed bugs) altogether bug count was up to 29,263 bugs. In addition there were 5,188 un-triaged (unconfirmed) bugs listed in Bugzilla on Mozilla 1.2 release day.

Table 2. Increase of Mozilla Bugs. From Mozilla 1.1 to Mozilla 1.2

(Please see the Bugs Note sidebar below for explanations.)

Item

Targeted Bugs New, Assigned, and Reopened Bugs Untriaged (Un-confirmed) Bugs
26 Aug

(Mozilla 1.1)

12,301 26,856 4,161
26 Nov

(Mozilla 1.2)

12,512 29,263 5,188
Increase
211 2,407 1,027

On Mozilla 1.3a release day there were 29,548 open new, assigned, and reopened bugs listed in Bugzilla plus 5,493 unconfirmed (not yet triaged) bugs listed in Mozilla's Bugzilla. The targeted, new, assigned, and reopened Mozilla bugs count was up to 12,487. Please see Table 3.

Table 3. Increase of Mozilla Bugs From Mozilla 1.2 to Mozilla 1.3.

(Please see the Bugs Note sidebar below for explanations.)

Item

Targeted Bugs New, Assigned, and Reopened Bugs Untriaged (Un-confirmed) Bugs
26 Nov

(Mozilla 1.2)

12,512 29,263 5,188

13 Dec

(Mozilla 1.3a)

12,487 29,548 5,493
Difference 1.3a-1.2
-25 +285 +305

4 Mar 03

(Mozilla 1.3)

12,255 30,431 5,895
Difference 1.3-1.3a
-243 +1027 +482
Difference 1.3-1.2
-268 +1312 +787

Please see our Mozilla 0.9.9 release article for more information about, and a breakdown of, the targeted new, assigned, and reopened Mozilla bugs complex. For more information about how Mozilla bugs impact on the user experience please see our articles A Quick Look at Some Mozilla 1.0 Browser-Suite Annoyances, Bugs, And Issues, Mozilla 1.0 Browser Quick Look, and Mozilla 1.0 Browser-Suite's E-Mail & News Quick Look .

For more information about how Mozilla bugs impact on your privacy and system security please see our article Mozilla and Netscape JavaScript Bugs Compromise Privacy and Security.

Mozilla has bugs problems. The Mozilla developers have continually failed to get the bugs targeted to milestones fixed before the scheduled milestone branching dates. Moreover, the Mozilla developers do not seem to be very effective in keeping buggy code from getting into the development tree.

However, after the Mozilla 0.9.9 release, code-checkin practices had been tightened down somewhat. That seemed to be providing some reduction in the Mozilla runaway bugs problem. Unfortunately, lizards do not change their spots and Mozilla bug counts are worse than ever.

That is not to say that Mozilla lizards have not been busy fixing bugs. They have. But, that just points up the tremendous Mozilla bug problem.

Despite the many bugs the Mozilla lizards fix, bug counts are higher than ever. That suggests inadequate code-review and tree management. Buggy code ought to be eliminated before it ever gets into the Mozilla code-base.

Bugs Note: the distinction, targeted bugs, is important. Almost anyone can submit a bug to the Bugzilla database. Many bugs so submitted are duplicates of other bugs, unconfirmed, or otherwise not bugs that should be fixed or need to be fixed. However, in order for a bug to be targeted, it must be either submitted or reviewed by a Mozilla developer or triager that has the appropriate skills and permissions level in Bugzilla to set the target parameters for bugs. This also applies to bugs listed as new, assigned, and reopened -- those parameters can be set only by a Mozilla developer or triager that has the appropriate skills and permissions level in Bugzilla. When we query Bugzilla for bugs targeted to a specific Mozilla release, we also restrict that query to new, assigned, and reopened bugs. Incidentally, the general query for all new, assigned, and reopened does include bugs related to other-than-Mozilla projects such as Bugzilla, Web tools, and so forth. That is one reason we do not report that bug in our Front Page bug-count tracking.
The preceding bugs discussion has focused on the impact of Mozilla's bugs on the development process. Just as important as that, if not even more important, is how the Mozilla bugs hit users.

If the Mozilla bugs for the most part are trivial or only rarely occurring, then end-users likely are not going to be very upset by the bugs. However, if the bugs are more noticeable, annoying, disruptive, or result in data loss, system crashes, or application lock-ups, then users likely are going to be rather upset.

That said, the more bugs in a program the more likely users will notice them and the more likely they will be annoyed by them. Bugs in milestone development releases are understandable although not a good thing.

Incidentally, a Bugzilla query today for open bugs with the keyword crash turned up more than 700 hits. A similar query made today using the keyword dataloss turned up more than 180 bugs. That's not a very pretty picture either.

All this bug stuff can be confusing. The most important point is that Mozilla 1.4 includes not merely the bugs targeted to Mozilla 1.4. Rather, Mozilla 1.4 includes some 31,000 un-fixed new, assigned, and reopened Mozilla bugs. The Mozilla 1.4-targeted bugs is merely a subset of the more than 31,000 un-fixed new, assigned, and reopened Mozilla bugs.

Please see our 0.9.4 branching article, Mozilla 0.9.4 Branched -- Behind Schedule & Buggier Than Ever, for more detail and information about the Mozilla bugs.

Mozilla post-1.0 Milestone and daily development builds normally are available for the BSD, Linux, Macintosh, Microsoft Windows, OS/2, Sun, and several UNIX platforms. Source code usually is available if you want to custom compile your own Mozilla builds.

Incidentally, please check the MozillaQuest Magazine front-page (mozillaquest.com) sidebar every now and then for bug-count updates and for upcoming Mozilla Milestone progress updates.

Please see our article, Mozilla Roadmap Update: Mozilla 1.0 Set Back to April 2002, for more information about the October 2001 Mozilla Development Roadmap and development schedule revisions. There is lots of bug information in that article too. For the first revised post-Mozilla 1.0 development roadmap and plan please see our articles, Moz 1.0 April Release Confirmed & Post-1.0 Development Plan Announced and New Mozilla Roadmap Sets 1.1 for 9 August 2002 and Effectively Kills Mozilla 1.0.x

The latest Roadmap revisions are discussed in our article, Major Morphing in Mozilla Project Organization and Objectives Proposed -- Part 1: Mozilla Management Reorganization and Splitting the Browser-Suite into Stand-Alone Products.


Downloading & Installation Info


Note: the Mozilla Organization used to include a simple, non-talkback, Milestone download build for the Microsoft Windows platform such as mozilla-win32-1.2.zip plus a talkback build. The Mozilla 1.4 release notes also call for such a mozilla-win32-1.2.zip build file and a talkback build file, mozilla-win32-talkback.zip.

1. Click the mozilla-win32-talkback.zip link or the mozilla-win32.zip link to download the .zip file to your machine. (Mozilla 1.4 Release Notes , the Mozilla Organization, 30 June 2003.)

Unfortunately, the Mozilla Organization has decided not to give you that choice for Mozilla Milestone 1.4. It has not included the non-talkback mozilla-win32-1.4.zip build -- even though the release notes say it is included.

The Mozilla Organization's rationale is that it needs the talkback info to get rid of bugs in Mozilla, particularly crash bugs. Getting rid of Mozilla bugs certainly is a noble purpose. And Mozilla has lots of bugs that need to be fixed.

However, freedom of choice is an even more noble pursuit. Moreover, choice is much of what Open Source Software is all about. Therefore we think the Mozilla Organization should have included the non-talkback mozilla-win32-1.4.zip too. Whether you participate in Mozilla talkback should be your choice, not the AOL-Netscape-Mozilla Organization's choice.

Of course you can turn talkback off when you install Mozilla if you use the installer version 1.4 Mozilla Milestone build (mozilla-win32-1.4-installer.exe). However, the installer version of Mozilla presents some potential privacy breaches, which we shall address eventually in another article.

In the meantime, we recommend that you disconnect your computer from the Internet when installing mozilla-win32-1.4-installer.exe so that you can adjust your security and privacy preferences before taking Mozilla 1.4 online for the first time. (Please see our article How To Download, Install, & Configure Netscape 6 -- Safely! for more about that.)

1.4 Download Links

Here are the FTP download links for Mozilla 1.4 for you readers that cannot wait to try Mozilla 1.4

Linux Builds



Windows Builds

Please see the important note in the sidebar to the right here before installing.

------>>


Tabbed-Browsing Comes to KDE

Major Morphing in Mozilla Project Organization and Objectives Proposed -- Part 1: Mozilla Management Reorganization and Splitting the Browser-Suite into Stand-Alone Products.

Mozilla 1.0.2 Browser-Suite Released -- Mozilla 1.0 updated!

Mozilla 1.3a Browser-Suite Released

Mozilla 1.3a Browser-Suite Released


Mozilla 1.2.1 Browser-Suite Released

Mozilla and Netscape JavaScript Bugs Compromise Privacy and Security


Mozilla 1.0-RC1 Browser-Suite Sneak Preview

Mozilla 1.0 on the Way -- Milestone 1.0-RC1 Branched


Netscape 6.2.2 Browser-Suite Released

Is Mozilla Actually AOL-Netscape's Mozilla?


Mozilla Milestone 0.9.9 Branched Behind Schedule


Year 2001 in Review -- Mozilla and Netscape Browsers

Mozilla Roadmap Update: Moz 1.0 April Release Confirmed & Post-1.0 Development Plan Announced


Mozilla Roadmap Update: Mozilla 1.0 Set Back to April 2002



AOL 7.0: Good News for AOL Users & Microsoft - Bad News for Netscape & Mozilla


Netscape 6.2.1 Browser-Suite Released

Netscape Communicator 4.79 Browser-Suite Released

Netscape 6.2 Browser Source Code (Mozilla 0.9.4.1) Released

Netscape 6.2 Browser-Suite Released

Netscape 6.2 Browser-Suite Coming Soon?

Netscape 6.1 Browser-Suite Released, Again?


Mozilla 0.9.x Releases & Download Links


Mozilla Milestone 0.9.8 Browser-Suite Released

Mozilla Milestone 0.9.7 Browser-Suite Released

Mozilla Milestone 0.9.6 Browser-Suite Released

Mozilla Milestone 0.9.5 Browser-Suite Released


Mozilla Milestone 0.9.4 Browser-Suite Released

Mozilla Milestone 0.9.3 Browser-Suite Released

Mozilla 0.9.2.1 AKA Netscape 6.1 Browser Source Code Released


Mozilla 0.9.3 Branched Behind Schedule & Buggy

Mozilla Milestone 0.9.1 Browser-Suite Released

The Snail Moves: Mozilla Milestone 0.9 Browser-Suite Released


Mozilla Roadmap

More Mozilla Roadmap Plan Changes and Chaos - Mozilla 0.9.2 Set for 25 June Release (June Roadmap revisions)

Mozilla Roadmap Plan Changed Again -- Mozilla 1.0 Set Back to Q4 2001 (May Roadmap revisions)

More Mozilla Roadmap & Development Plan Changes: Mozilla 1.0 Pushed Back to Q3 2001 (April Roadmap revisions)

Mozilla 1.0 Release Pushed Back -- Milestone 0.8.1 Inserted into Development Roadmap Schedule (March Roadmap revisions)

Mozilla Organization Revises Development Roadmap and Product Release Schedule (December Roadmap revisions)


Mozilla 0.8.x Releases & Download Links

Lizard On The Move: Mozilla Milestone 0.8.1 Browser-Suite Released

The Lizard Marches On: Mozilla Milestone 0.8 Browser-Suite Released

Mozilla Milestone 0.8 Browser-Suite RPM Builds Released


Other Related Mozilla & Netscape Articles

Composer: The Netscape & Mozilla Graphical HTML Editor & Word Processor

Netscape 6.1 Browser-Suite Released Again?

How To Download, Install, & Configure Netscape 6 -- Safely!


MozillaQuest the Series: Building Your Own Mozilla-Based Web Browser

Meet Bugzilla -- Mozilla's Secretary of Bug-Busting & Feature Requests Lizard


For more information about the Mozilla Organization, the Mozilla applications programming framework, and the Mozilla browser, please see:

Please do not forget to report bugs, problems, or suggestions for enhancements to Bugzilla.

For more information about the Mozilla Roadmap & Milestone Plan, please see:

Mozilla Development Roadmap

Help Using The Bugzilla Query Form


Copyright 2000-2003 -- MozillaQuest -- Brodheadsville, Pa.. USA -- All Rights Reserved

Recent Articles

Mozilla 1.4 Browser-Suite -- AKA Netscape 7.1

Gaël Duval and Mike Angelo Discuss Mandrake Business Products and Finances

SuSE Linux Desktop Available

About the Hey SCO, sue me Petition

Mandrake Linux 9.1 Retail Packs

Linux for Windows Users -- Linux Networking for Windows and Desktop People -- Mandrake 9.1 and LinNeighborhood

Gaël Duval and Mike Angelo Discuss the New AMD64 OS --

Mandrake Linux Corporate Server 2.1 for AMD Opteron

SuSE Linux Enterprise Server 8 for AMD64 Released

Major Morphing in Mozilla Project Organization and Objectives Proposed

Red Hat Linux 9 Distribution Released

Mandrake Linux 9.1 Released

SCO-Caldera v IBM:

Mandrake 9.1-RC1

Netscape 7.02 Browser-Suite

SCO-Caldera & the GNU/Linux Community: The SCOsource IP Matter

LinuxWorld in New York City -- 21-24 January 2003

Don't Forget the Books

Linux Makes a Great Gift

Christmas Season Holidays & Computer Suggestions 2002

Netscape 7.01 Browser-Suite

Mozilla 1.2.1 Browser-Suite Released

Buggy Mozilla 1.2 Recalled

Mozilla 1.2 Browser-Suite Released

Mandrake Linux 9.0, Desktop Magic You Can Use: A First Look

Mandrake Linux 9.0 Retail Boxes Ship

Linux for Windows Users:

Using LinNeighborhood to Create a Network Neighborhood for Linux

SuSE 8.1 LSB Certified

SuSE Linux 8.1

Zero Tolerance for Privacy and Security Bugs

Mozilla and Netscape JavaScript Bugs Compromise Privacy and Security

Red Hat Linux 8.0 Is LSB Certified

Red Hat Linux 8.0

Mandrake 9.0 is LSB Certified

Mandrake Linux 9.0 Released

SCO's Darl McBride and MozillaQuest Magazine's Mike Angelo Discuss Caldera Linux and LSB

Caldera/SCO 3.1.1 OpenLinux Distribution Gains LSB Certification

UnitedLinux: A Standard or a Distribution?

UnitedLinux, a Divisive Weapon for Caldera's Darl McBride -- Part II

Holger Dyroff, Gaël Duval, Mark de Visser and Mike Angelo Discuss LSB, UnitedLinux, and the Linux Market

UnitedLinux, a Divisive Weapon for Caldera's Darl McBride -- Part I

Netscape 7.0 Browser-Suite

Netscape Communicator 4.8 Browser-Suite

Red Hat Calls on Linux Comunity for Beta Feedback

MandrakeSoft Calls on Linux Community for Beta Testers

Mandrake 8.2, Red Hat 7.3, & SuSE 8.0 Linuxes now LSB Certified

Scott McNeil and MozillaQuest Magazine Discuss LSB

Are You Ready For the Linux Standard Base? LSB is Ready for You!

SuSE Says Yes to LSB and UnitedLinux

New Mozilla Roadmap Sets 1.1 for 9 August 2002 and Effectively Kills Mozilla 1.0.x

MandrakeSoft Says Yes to LSB but No to Netscape and UnitedLinux

Red Hat Drops Netscape

Mozilla 1.0 Browser-Suite's E-Mail & News Quick Look

Mozilla 1.0 Browser Quick Look

Tabbed-Browsing Coming to KDE's Konqueror Browser

A Quick Look at Mozilla 1.0 Browser-Suite Performance -- Speed, Stability, and Memory Hogging

Mozilla 1.0 is Officially Out!

A Quick Look at Some Mozilla 1.0 Browser-Suite Annoyances, Bugs, And Issues

Mozilla 1.0 Not Ready for Prime Time -- Close but No Cigar and No Brass Ring!

Turmoil in MozillaLand:

Mozilla 1.0 Browser Unofficial Sneak Release

AbiWord 1.0.1 Quick Look - MS Word Clone for Linux, MS Windows, & Other Platforms

Mozilla Roadmap:

Mandrake Linux 8.2 Boxed-Sets Available -- Update -- KDE 3.0 Upgrade & StarOffice 6.0

KDE 3.0 Released

MozillaQuest Magazine 2001 Editor's Choice Hardware Picks

Mozilla Roadmap Update:

Moz 1.0 April Release Confirmed & Post-1.0 Development Plan Announced

Getting Started with Wireless Network Technology

Part III: Adding Wireless to a Linux-Based Laptop or Notebook

Is Mozilla Actually AOL-Netscape's Mozilla?

Bugzilla 2.16 & Bugzilla 2.14.1

Year 2001 in Review -- Mozilla and Netscape Browsers

Free Software for Your New Christmas Computer -- Or Any Computer for That Matter

Linux Gifts for Christmas, Holiday, and All Occasions