Slashdot Mirror
Mozilla 1.4 RC1
Mister.de writes "Mozilla 1.4 RC 1 is out. We've added lots of features and fixed lots of bugs since Mozilla 1.3. Help us shake it down in preparation for Mozilla 1.4 final. More information is available in the release notes. Mozilla is an open-source Web browser, designed for standards compliance, performance and portability."
Some links:2 1639.html
h tml?tag=nl
"Does Netscape Deal Mean 'Game over' for Open-Source Browsers?"
http://www.newsfactor.com/perl/story/
Microsoft pays AOL 750Mil for killing Netscape. Gives 7 year license to use Microsoft Internet Explorer:
http://news.com.com/2100-1032-1011296.
Perhaps someone from the Mozilla project will read this...
I notice that there's an IRIX version of Mozilla available from the nightly build collection, yet there is no IRIX version on the offical releases page. I know SGI maintains a port of IRIX on their OSS and freeware sites, but these are usually out of date. I think it would be nice to see an IRIX download of the final releases on the actual Mozilla site. If the hardware already exists to build the nightlies, I wouldn't imagine it would take much time or effort to build and tar up the final versions for download as well.
Or at the very least, how about add the links to SGI's two download sites to the Mozilla release notes. OpenVMS is even listed!
Just my $0.02. I've been using the nightlies for a few weeks now and am very happy with the progress that has been made since Mozilla 1.0.
NTLM works, but not on 98. Works fine in NT and 2k. So to say it works is a little disingenuous. And yes, I did post this to bugzilla.
m.kelley
life is like a freeway, if you don't look you could miss it.
Probably the coolest change of all in this release, is the ability to build Mozilla for Windows using only GCC! Whoo hoo! No more VC++ crap! Can we get a build for Cygwin/XFree86 next? That way those of us forced to use Mickeysoft can go all Unix software!
Javascript + Nintendo DSi = DSiCade
I'm posting with my fresh and shiny 1.4 RC1, and I have to say that the subjective speed is increased significantly over 1.4 beta.
It feels on par with opera now...
Congrats to the mozilla team
Btw... why is RC1 announced on slashdot? wouldn't it make more sense to kick their ftp servers in the nuts when 1.4 is finalised?
Firebird is NOT exactly a fork. According to the page (OK, I've read it somewhere, old phoenix's page, I think), to make a Firebird build they get the latest CVS Mozilla and patch only the interface code. This way, if some change in RC1 is deeper than interface, then it is automagically in the next Firebird. You can see this if you go to about:config in Firebird. You'll see (should I say legacy) options for about everything in Mozilla (mail/news, composer).
Mozilla and Firebird both use the exact same engine - Gecko. And since Firebird is built off of the same trunk as Mozilla, the version, and hence capabilities, of Gecko are the same. Almost all of the differences between the Mozilla Application Suite and Mozilla Firebird (to use the correct terms) are UI and removal of non-browser components.
If all the world's a stage, anyone who says they want better lighting spends far too much time in a dark theatre.
See, they just use the Windows dll, and if that gets updated, Mozilla should just be able to get things done.
Good thought, bad example.
Get Firefox!
There's been a lot of discussion about how Mozilla 1.4 will the be the last version in it's current form, as Mozilla 1.5/2.0 will be based on Firebird... Keep in mind that one of the goals for 1.4 is to replace 1.0.x (currently 1.0.2) as the stable distribution version. So while future versions will have drastic changes to the GUI framework, 1.4 will live on with small fixes for those that aren't needing or wanting the very cutting edge. Just as there are many current unix and linux distributors shipping 1.0.2 today, there will be many shipping 1.4.x a year from now. As for the version number discussion, my vote is to call the next version 1.5... I think the version 2.0 title should be reserved for a refined, heavily tested version of Firebird. Much like the extensive testing that went into the current flavor of Mozilla before 1.0 was released. Maybe I just don't like version number bloat...
one small bug with mozilla 1.4x and win xp is that when you try to save a file mozilla will add stuff to the file name, for example file.mpg will be saved as file.mpg.mpeg. that by itself isnt a problem but when you run across a file like file.avi.torrent mozilla insted of launching bittorrent will try to save the file as file.avi.torrent.avi which is a pain in the ass
You're right, they're not. So I suggest that you complain to ATI that their graphics card driver is full of bugs and can lead to random crashes of applications that use graphics in a serious way. They already admit that the problem is at their end so you may as well let them know that you find it unacceptable.
For what it's worth, I'm not sure if this particular crash is actually still happening. It's been in the release notes for ages, but I don't recall many reports of it happening recentley. Maybe it's been fixed by the latest driver upgrade.
Calling the next Mozilla release 2.0 will not be justified. Although Mozilla Firebird will have a completely new ui, Mozilla does not consider such things important for releases. After all, it's not an end-user product.
If you remember the Mozilla 1.0 Manifesto, you'll see that one of the most important point of that release is:
So unless and until we go break the APIs, or do other major work at that level of the program, there is not yet a reason to call it Mozilla 2.0. Because once again, it's not the occasional end-users which are Mozilla's customers, it's the people embedding Mozilla in various products, the people distributing releases based on Mozilla. And those don't care about some silly little front-end changes.
If potentially getting absolutely buggy and alpha builds doesn't appeal to you, you won't want to download builds from latest/ - you'll want to download from latest-1.4/
This is hardly incremental. The inclusion of NTLM is a monumental advance. It means I no longer need to use IE on my intranet which uses NTLM for everything.
Double right clicking on a page can disable the keyboard.
That's bug 30841 and it was fixed a year and a half ago. It's still in the release notes because the wrong bug number was listed in the release notes, and the semiautomatic check for fixed bugs (which I believe involves Asa using the "collect buglinks" bookmarklet on the release notes and scanning for fixed bugs) didn't catch it.
Please don't judge Mozilla's stability based on the release notes. Instead, judge Mozilla's stability based on how often it crashes when you use it. (Some Mozilla developers have access to MTBF statistics from Talkback, but that's most useful for determining the relative stability of different Mozilla releases.)
The shareholder is always right.
Two things:
:) Once we're happy that the last bugs are squished, it will most likely replace wu-imapd on our site IMAP servers.
1) There is an internal Mozilla preference to tell Mozilla to check *all* IMAP mailboxes, rather than just your INBOX. Enter ``about:config`` in the address bar and create the following boolean pref:
mail.check_all_imap_folders_for_new
and set it to ``true``.
2) IMAP is not client-side check only -- the protocol allows for server-side checking and notification. Have a look at the new GPL IMAP server called Dovecot which has support for this.
Although it's not been released as stable yet, it's current version number is 0.99.9.1 (sound familiar?
Cheers,
David
before you dl next time check out the roadmap table near end of page to see the estimated dates for the next release.
version 0.0002