Full Article Attached Mozilla 1.1 Branching Update

Saturday August 3rd, 2002

Yesterday evening, Asa Dotzler posted an update on Mozilla 1.1 to netscape.public.mozilla.seamonkey. The current plan is to branch for 1.1 and reopen the trunk on Monday. Read the full article for more information and check out Asa's recent posting to the Build Bar forum to see how you can help.

#1 Whatever

by Tanyel

Saturday August 3rd, 2002 6:44 PM

The browser will become much more competitive when it can be upgraded as easily as America Online. I think that and a suitable download manager would make a bigger difference than anything else right now.

#18 Re: Whatever - download manager & spell checker

by VMD

Monday August 5th, 2002 2:45 PM

I would like to see a download manager like Download Accelerator Plus (but without the advertisements, of course) which breaks a file into 5 pieces, downloads them and puts them back together. Mozilla downloads much faster for me when I use DAP, instead of the "right click > Save Link Target As" routine.

I have no complaints with the upgrade process, but it would be nice to have a "bright little flashing icon" appear somewhere on Mozilla, or the delivery of an email, when there is a new release/milestone (1.1, 1.2a, 1.2b, 1.2, etc.). The "bright little flashing icon" can go away once it has been clicked. This would be real cool, slick.

I would like to see a spell checker that is both usable in mail AND within the browser (forums, dialogue & discussion groups).

#19 Re: Re: Whatever - download manager & spell checke

by jsebrech

Monday August 5th, 2002 4:13 PM

"which breaks a file into 5 pieces, downloads them and puts them back together"

This is not very polite to other netizens (to say the least) when you're on any sort of broadband connection (which is the only kind where this pays off). If you're on cable you're hugging your local loop. And unless you're downloading from a fast server it's going to be taxed from your five-headed hydra attack, leaving the rest of the downloaders stranded with a slower download until you're done.

I should talk though. I used to do this myself.

"I have no complaints with the upgrade process"

Definitely not a modem user. Remember it takes an hour on the fastest modem connection to do a full download of mozilla. Most connections do half of that. When for every mozilla download you have to wait almost 2 hours, I can imagine that after a while you say: "why bother?" You're not going to be tracking nightlies, that's for sure.

#2 The stability of 1.1

by robdogg

Saturday August 3rd, 2002 7:57 PM

I am kind of worried about the stability. I was sorry to see Asa stop doing the updates, because I would guess not as many people would download a nightly build without knowing whether it is a good one or not. As a result, not as many eyes see it and not as many people file bugs. Perhaps someone else could pick up the slack from Asa?

#3 I agree

by sbutler

Saturday August 3rd, 2002 11:53 PM

I run nightlies all the time, but since he stopped doing his updates I have stopped downloading them. I am not blaming Asa, I know he is busy, but it would be really nice if someone could take his place.

#4 Re: The stability of 1.1

by asa

Sunday August 4th, 2002 12:37 AM

robdogg, there are literally tens of thousands of nightly builds downloaded every day. That number has not been significantly impacted by my not updating the buildbar. Our talkback and bug data (as well as feedback from adhoc testing) point to greater stability than 1.0.

So don't be kind of worried. We've got it under control.


#5 Re: talkback don't catch important bugs

by cktwo

Sunday August 4th, 2002 2:29 AM

For instance, if opening a link from mail, most times if there is form data, there is no way to get a cursor into the form boxes. Talkback's don't catch bugs like these.

#13 Re: Re: talkback don't catch important bugs

by asa

Monday August 5th, 2002 12:55 AM

talkback isn't designed to catch those bugs. talkback is designed to help us track stability and root out crash bugs.


#6 Re: Re: The stability of 1.1

by borggraefe

Sunday August 4th, 2002 3:40 AM

How does the stability of a current nightly from the 1.0 branch compare with a current 1.1-build?


#10 Re: Re: Re: The stability of 1.1

by jonasj

Sunday August 4th, 2002 7:50 PM

The trunk is generally more stable than the branch.

#11 really?

by bandido

Sunday August 4th, 2002 9:03 PM

Isn't it supposed to be the othr way around. The trunk usually receive higher risk changes than the branch.

#12 Re: really?

by asa

Monday August 5th, 2002 12:54 AM

The trunk has taken higher risk changes. Some of those large changes allowed us to simplify and clean up code that was fragile leading to improved stability. The trunk and the branch are about the same when it comes to overall stability. The trunk has a couple crashers the branch doesn't have and the branch has a couple of crashers that the trunk doesn't have.


#7 On (pre) Mozilla 1.1

by JayeshSh

Sunday August 4th, 2002 10:06 AM

Hello all,

I've had the chance to try out the pre 1.1 nightly builds that Asa recommended - and I am very impressed. I think 1.1 will be really, really good. (I hope Netscape 7 is based on Mozilla 1.1 and not 1.01, because 1.1 seems so much better.) There seem to be many improvements in Composer - many which you don't see at first. I've only had one crash until now.

I've made a list of what's new and cool in 1.1, and put in on my MozTips site:


(Plus I have a new Quality Assurance Glossary on my site too ... )


- Jay

#8 Re: On (pre) Mozilla 1.1

by MXN

Sunday August 4th, 2002 11:02 AM

"I hope Netscape 7 is based on Mozilla 1.1 and not 1.01, because 1.1 seems so much better."

I don't think that Netscape would release Netscape 7 based on 1.1, because they already had the 6.0 fiasco, so they would probably would want the most stable product possible to release on. Of course, I don't work at Netscape, so I wouldn't know. :^)

And the corrected link, by the way, is .


#9 thanks for the correction :-)

by JayeshSh

Sunday August 4th, 2002 3:17 PM


Thanks for the correction - I surrounded the links with less than and greater than signs, thinking that would make it clickable; but I guess it had another unintended effect.

Hmm ... I wonder what Netscape 7 will be based on ... All I know is that it gets very quiet, something is brewing. And it just might be a brand new Netscape 7 (purely my speculation).


- Jay

#14 1.0.1

by Salsaman

Monday August 5th, 2002 4:54 AM

What happened to 1.0.1 ? Shouldn't it have been out a couple of weeks ago - is there some big problem that is holding it back ?

#15 Re: 1.0.1

by turi

Monday August 5th, 2002 9:13 AM

It looks like some sort of cookie related security bug is holding it back. But others probably know more.

#20 Re: Re: 1.0.1 - cookie problem

by treebeard

Monday August 5th, 2002 11:57 PM

the cookie bug has been reported on bugtraq ( 7/24 ) by Andreas Sandblad I don't know if it has been fixed. The security related bugs are usually blocked on bugzilla at least until they are fixed. Understandably. One doesn't want to encourage exploits.

in pertinent part:

DESCRIPTION: ============

Mozilla allows script in the javascript protocoll to set and read cookies. For javascript URLs the host and path for the cookie is pulled out as: "javascript:[host][path]"

......., it is possible to access and alter cookies from other domains.

#16 why mozilla does for me


Monday August 5th, 2002 11:14 AM

yes, you might be right. they could have released some of the 1.0branch stuff already. but then you could also pick it up for yourself. there are dayly builds of the branch. sure - there are not that many new things in there as in the trunk, but they are there.

to track the release of 1.0.1 there is the "make mozilla 1.0.1 not suck"-bug at and you should also take a look at the revised roadmap at to see that 1.0.1 is scheduled post 1.1 so stop whining

#21 Hey I wasn't whining !

by Salsaman

Tuesday August 6th, 2002 3:48 AM

Just being curious. I am using the 1.1 branch anyway.

#17 Re: 1.0.1

by asa

Monday August 5th, 2002 11:27 AM

There are no big problems holding it back. It's nearly done and it will be released when it's ready.