Mozilla 1.4 RC3 Is Out
zzxc writes "Mozillazine reports that the third release candidate for Mozilla 1.4 has been released. It is available for download from mozilla.org. Testing is encouraged to fix any bugs before the final release. No new features have been added to this release, though many bugs have been fixed. For more information, see the release notes."
you forget those of us who use the mail client. firebird doesnt have mail/chatzilla/etc.
Since RC1 there are no source tarballs available and there are no tags to fetch it through CVS.
I wish they would only put in the release notes the changes between RC2 and RC3 (and not between 1.3 and 1.4). Every time I read the release notes for the different RC's I get a strong dejavu. Must I really begin to diff them?
Now if I could only find some RedHat 8/9 RPM's to make it all hassle free
/bin and point it at the correct location... I found that by simply NEVER installing mozilla from redhat's install process you fix what redhat breaks, and the installer works great.
Oh come on....
it's too difficult for you to download and run the installer?
granted because of redhat's brain-dead policies of putting things where THEY DONT BELONG means you have to simply delete the symlink in
Let me guess, you also think that installing Open Office is too difficult...
Do not look at laser with remaining good eye.
I second that. But that would defeat the purpose of getting lots of beta testers.
You mean, something like freshmeat.net?
Teenagers these days don't have as much sex as they want each other to think they do.
Erm, I'd say ANY release candidade is expected to be the final. Otherwise, why's is it a candidate? In my book, RC means you've fixed all bugs you're aware of at that time, so unless some others crop up, that's going to be the final version.
Be wary of any facts that confirm your opinion.
But that's how it SHOULD work. A release candidate is a build which is expected to become the release. If you expect that it won't be the final build, it's a beta version, not a RC. You can trick users into installing RC builds a few times, but when they realize that the builds are just more "public betas", they will stop installing RCs and that will remove this important step from the feedback loop. Calling a build more mature than it is is also a bad move publicity-wise. People expect that the release is mostly the same as or only slightly better than the release candidate, so if you know about bugs which you deem inacceptable for a release build, don't make a release candidate before fixing them.
If I am saying 1.3.1 i do not say nightly build.
/. . They are trying to help you, but if a bug exists "uninstall first" this is what they will always reply, even if the problem the reporter is heaving has nothing to do with XDOM dllÂs
1.3.1 happens to be the previous stable release. As is said in the comments of this bug: Why cannot clean the installer the old directory.
Answer from developer:
How to prevent data-loss if something (user-mail) is in that directory.
i think if you leave this to the user he sure is going to delete the wrong data.
AND YES I AM WORKED UP ABOUT THIS. Try posting something about a bug here on
Mozilla Firebird is designed around the idea that choice is a good thing. That's why it's lightweight with a powerful customization and extensions system. These GUI features that are relatively small but (apparently) important could be implemented as extensions.
Those 'handful of "elite" developers' are the ones coding the project. As in any open-source project, if you don't have code to contribute, your opinion is only important if the people that DO CONTRIBUTE code think it is. If those "elite" people won't accept the code you write, turn it into an extension and keep the xpi floating around your desktop to install when the new version comes out. If you don't like having to update the xpi's format whenever Mozilla Firebird's API changes, then you know why the developers don't want to code features they won't use.
"[We'll be] really getting inside your head and making it an unpleasant place to be" -- Trent Reznor
Try telling here (i am not talking about bugzilla in the "every bug line) about some bug. They will point to the release notes:
"Install into a new empty directory. Installing on top of previously installed builds may cause problems."
That is an easy way to work around bugs. Just say "donÂt do that" in the readme.
And yes, i think it is strange there are critical bugs in a release candidate. These should be demoted to not important or the thing should still be called a beta.... AND/OR the bug should be explained in the readme. Still time for a 1.4.1. RC4 ?
(by the way, if you think that was a troll then never reply to it.)
nice, but that would require me to navigate to the googlebar, type something there and press enter. I don't want to navigate to the googlebar, i have my addressbar already which is quite suitable for this task as well. I consider the googlebar rather to be "bloatware". Don't need the extra inputbox sorry :)
Er...
Control-L <keywords> -> Google "I'm Feeling Lucky" for keywords
Control-K <keywords> (or Control-L <tab> <keywords>) -> Google search for keywords
I don't think I understand what's your problem...
Prescriptive grammar:linguistics
they would have to change it to the Mozilla style google search of course. ... all soooo unnecessary with the wonderfull mozilla feature.
The whole point of my rant is that i want to be able to search google and i want to do this *quick*, that means the less keys i have to press the better. Now when using the goto or google keyword i would have to type that in wouldn't I ? If i copied something from the clipboard and want to search for it then i would have to prepend this keyword to the searchstring
What do you mean you don't want to switch search fields??? You obviously had to consciously say "I want to do a search" at some point and click on the address bar before you typed the search terms, the location bar does not constantly have the keyboard focus. What difference does it make if you click the address bar or the search box?
Because most people LIKE a dedicated google search field (hence the popularity of the google toolbar for IE). And besides, if you dislike it that much, rip it out and use keyworded bookmarks instead.
And as someone else pointed out, you can add a google bookmark with a "g" keyword. Only requires two keystrokes "g " in addition to the keywords themselves. So firebird does not need three keystrokes to do the job.
Just how many of you download and compile every single version of Mozilla that's mentioned on /.? /. effect) and it takes time to compile. Very few bother to go through this process for every release.
/. effect, wouldn't that mean that a lot of people are downloading it???
It takes time to download (due to the
If the downloads are suffering the
I think it would help immensely to put together a deb package that had Firebird / Thunderbird that installed it properly, put it in the menu, integrated it into Gnome, etc. There's plenty of debian users that would run it, at least alongside their other browser/email, but don't want to do an installation themselves. Bug reports and feature requests come from such users.
Firebird and Thunderbird current can't share the same Gecko runtime. So if you use both you're getting two copies of the Mozilla core loaded into memory. Might as well stick to Mozilla until that changes.
Has anybody noticed that Firebird gets progressively slower as your cache increases? I find that when I do a fresh install, the browser is snappy, and generally faster than IE. Over time, however, I am forced to wait up to 5 seconds to load a page from a fast web server only a few hops from me.
Clearing the cache seems to fix the problem somewhat. I also reduced the disk cache size to 5MB. Has anyone else had a problem like this?
"Smoking helps you lose weight - one lung at a time" -- A. E. Neumann
I won't install RC3. To me it's just another beta. Maybe it's not, but I can't tell anymore, because the other two release candidates were clearly betas. If someone asks me whether he should install a RC or wait for the release, I'll tell him to wait for the release (maybe a few days longer to see if it's not a 1.2), because release candidates are really testing releases with known severe bugs and therefore not suitable for users. When the bughunting drift from beta to release candidate results in general disinterest in release candidates, are you going to call them final and fix the bugs in the next release? Watch out, I think Microsoft has a patent on misleadingly tagged public beta releases.
Mozilla Firebird is designed around the idea that choice is a good thing.
No, it is not. If it was, it wouldn't cut dozens upon dozens of features that people use everyday and which do not harm people who don't use them.
Dozens? Really? Like "at least 24"? Exaggeration doesn't help your point. There are not 24 features in SeaMonkey which are not in Firebird. I have a hard time counting more than a small handful. Differently presented features are not cut features.
I'm certainly no usability expert but if you really think that there's no harm to usability when you add lots of features which clutter and confuse UI then you don't have a very good understanding of usability.
And TBE is not the favorite extension of all Firebird fans. It's a popular extension but most Firebird users have probably never installed a single extension. Once again your exaggeration doesn't help make your case.
--Asa
I haven't seen a MacOS 9 binary release for a long time... not since v1.2.1 anyway. Am I left to compile on my own or has the Mozilla project dropped support altogether?
Lets see, all of these things are not really a browser, are they? When I asked what features, I was asking what *browser* features you thought were missing.
I would love to switch, but unfortunately it is not suitable for my requirements yet. I'm sorry if this upsets you but it's a plain fact.
I applaud you for finding something that fits your requirements. All I took issue with is that you assumed that *everyone* needed your requirements (a big boatload). Lots of people only need a fast browser, and I am one of those people. Mozilla does not cut it for me. Firebird is the fastest thing I've used, aside from Opera, and is therefore my choice.
Make sure everyone's vote counts: Verified Voting