Tree Closes Tonight for Mozilla 0.9.9
Tuesday February 19th, 2002
mozilla.org will begin the process to release Mozilla 0.9.9 tonight at 11:59 pm pacific by closing the tree to free checkins. Mozilla 0.9.9 is the last major milestone prior to 1.0, and includes numerous bugfixes in composer, history, and other areas. Along with this, likely new features that will be in the milestone include a new full screen window mode, set image as wallpaper, and composer publishing.
Following the tree close tonight, expect up to a week of tree closure for stability and regression fixes, then a branch to be cut some time next week. As soon as the branch is cut, the trunk will reopen for Mozilla 1.0 checkins. mozilla.org is shooting for a March 1st release date, but due to this being the last milestone before 1.0, and because there is a large amount of code that will be landed tonight prior to tree close, delays may occur.
#163 Re: Re: Re: Re: Re: View-source still not fixed :(
Wednesday February 27th, 2002 9:15 PM
You are replying to this message
<<Clue 1: "Wow. I'm really hyped about this new uberbrowser. Lemme just shut everything down so it will run acceptably.">>
Yes, Moz is big on the memory side. My work box has a nightly build in the 20-30 Meg rage now, as opposed to IE 5.5's 10-15 Megs. No argurment there.
<<Clue 2: "Funny, this works in every OTHER CSS/JS/whatever-capable browser I've tested it in.">>
Perhaps they were using code that's IE-specific? If not, perhaps it's a bug. Given that Moz's CSS-compliance is generally rated as the best, neck and neck with Opera depending on the test, I'm wary of any pages that don't work. On my home Linux system, pages that don't work usually turn out to be IE-specific, and don't work on anything here (Mozilla, Opera 5 or 6, or Konqueror, although Konqueror sometimes makes it through)
<<Clue 3: "I remember this preferences dialog. I saw it back in 1998.>> How much has the interface for, say, IE changed? Who even remembers what version of IE was out 3 years ago? I'm unaware of why such a build of Mozilla should be seen as something to base current pratices on.
<<Clue 4: "Huh? Why does my page look like crap?">> I'l agree that some of the decisions on how to render pages are...odd. And I wish there was more docs on how to fix a legacy page for Mozilla. But, you know, it's possible that I can simply sit down, take the time out, and write the docs myself.
<<Clue 5: "Gee, now it won't even run at all.">> I've toasted IE installs in the not-too-distant past. Moz still needs lots and lots of help, but it's coming along. Also: Mozilla!=Netscape. I've heard pleasant things about the more recent Netscape releases, and I think it's a mistake to assume the whole project is down the tubes because the announced-as-beta-or-alpha-cutting-edge software doesn't work. Perhaps this means one should use less cutting edge tools, such as a Milestone build or the latest in the Netscape 6.x series.
Now, as far as "please, explain to me why I should take Mozilla seriously, if you can.":
Frankly, it's one of the two best browsers if you want to code to standards. That's enough for me right there, as a Web Designer. My goal, when I code, is to construct a web interface that people can use. Coding a site that works well in Mozilla is a strong indication that it'll work in every other browser out there, even text-based ones. The same cannot be said, always, of IE, esp. if you code using FrontPage.
"Gods help Mozilla when it hits Version 1. The wolves will tear it to shreds." Ah, yes, of course. Oh, wolves? Shread away!:
"CNET's decision: It's a tie! Who'd have thought? After adjudicating five rounds of convincing arguments, we ended up with a hung jury. True, Netscape won the popular vote hands down. But our traditional voting process demands that we call it a tie. (Fortunately, we didn't allow any room for a third-party browser, such as Opera, to snatch votes away from either contestant.)"
From <http://www.cnet.com/softw….bhed.3227883-8-7614087-1> . Keep in mind, that's IE 6 vs. Netscape 6.1. Netscape is up to 6.2 now.