Mozilla Firefox 1.5.0.4 Released
KrayzieKyd writes "God Bless Mozilla. Firefox has just notified me that Firefox version 1.5.0.4 has just been released with release notes and according to Mozilla's website, the same has been released for Thunderbird with its own release notes."
Are we getting slashdot articles for each verion bump of the mozilla products? I tought freshmeat was created for that.
Is there something special about this release? According to the release notes these bugs where removed. Great but not enough for a slashdot article.
MFSA 2006-43 Privilege escalation using addSelectionListener
MFSA 2006-42 Web site XSS using BOM on UTF-8 pages
MFSA 2006-41 File stealing by changing input type (variant)
MFSA 2006-39 "View Image" local resource linking (Windows)
MFSA 2006-38 Buffer overflow in crypto.signText()
MFSA 2006-37 Remote compromise via content-defined setter on object prototypes
MFSA 2006-36 PLUGINSPAGE privileged JavaScript execution 2
MFSA 2006-35 Privilege escalation through XUL persist
MFSA 2006-34 XSS viewing javascript: frames or images from context menu
MFSA 2006-33 HTTP response smuggling
MFSA 2006-32 Fixes for crashes with potential memory corruption
MFSA 2006-31 EvalInSandbox escape (Proxy Autoconfig, Greasemonkey)
200GB/2TB $7.95 Coupon: SAVE90DOLLAR
Seamonkey, the new version of the old mozilla suite (Netscape-like) has also been updated. The release notes: http://www.mozilla.org/projects/seamonkey/releases /seamonkey1.0.2/.
I thought one of the benefits of Firefox 1.5 was incremental updates i.e. patches that that are in the 100s of KBs range. However, watching the progress meter for this latest update it will have eventually downloaded 6.1MB, which is basically the full version of Firefox.
I've got a fever and the only prescription is more COBOL.
Not so much crashing but 1.5 seems slower. Especially noticeable with several (or many) tabs open. Systems I've noticed this on were not low end either. And OS did not matter, Windows XP, RHEL and Fedora all were sluggish. Seems like 1.0.7 offered a better all around browser experience.
I'd like to hear about memory management issues, frequent crashes and how Opera was there first - in that order. I need a refresher; it must be while since v1.5.0.3.
I think it's excellent with all these updates. Firefox if absolutely worth the attention.
Before Firefox - our local banking etc. where only accepted on Internet Explorer and nothing else, leaving out Mac and Linux users. Today Firefox is so respected that our country's Largest Bank support it!
Way to go FIREFOX!.
What this world is coming to - is for you and me to decide.
Is it just me or are the menus like 4 times faster at least? Or is it this patch changes firefox so that my old registry tweak setting windows menu paint dealy from 400ms to 0ms now being recognized by FF? I'ts not a simple memory leak fix because I have 1.5 gigs and I never noticed FF slowing down after long term use.
Or am I just crazy and nothing changed at all? maybe it was the extention update to cute menus cyrstal SVG
This is known and actually a feature, which can be turned off:
9 .html
http://weblogs.mozillazine.org/ben/archives/00974
[--- PGP key and more on http://www.root42.de ---]
And I *still* can't find text within a textbox...
Swedish plasma phys. PhD student; MSc EE; knows maths, programming, electronics; finance interest; seeks opportunities
Just tested with the newest macintel universal binary, and it is significantly faster than 1.5.0.2 (which also claimed universal binary, but they fucked up).
If you let software update happen on a mac intel, it doesn't update to 1.5.0.4 universal, but just updates the PPC image. You need to download the new universal image, and install that over the older version, and then it runs.
They still haven't addressed all the networking problems yet, but I really don't ever expect them to.
the AC
Hemos is like...sci-fi fans;he thinks technology is cool, but he hasn't bothered to understand the science it's based on
Anyone wanting to stick with the Mozilla Suite should upgrade to SeaMonkey soon for security updates. SeaMonkey gets all the core security fixes Firefox and Thunderbird do, but the old Suite isn't being developed any more and therefore won't get any security fixes.
What a fool believes, he sees, no wise man has the power to reason away.
Looking at the source code, you can see which code got changed and which changes were made. The bug is not for your eyes, as it may give detailed steps to exploit the vulnerability.
Remember when Microsoft releases a patch it would say "a maliciously crafted web page may" etc. The bugzilla entry for Firefox may actually GIVE you all you need to build that maliciously crafted page.
As said before, there's no need to publicize detailed steps to exploit a browser.
I am currently using Bon Echo Alpha 3 . I tried 1.5.0.4 and it seems much stabler and faster than 1.5.0.3 but it seems to me that Bon echo is still the best firefox version, It seriously is awesome.
Copyright infringement is "piracy" in the same way DRM is "consumer rape"
Considering that privacy and security are big concerns for every large software project these days, I believe that Firefox's default update setting should be changed. If you go to Tools --> Options --> Advanced --> Update, and you haven't changed your default settings, you will find that it is set to "Automatically download and install the update". Even Microsoft wouldn't do this, so why is it acceptable in Firefox? It should default to "Ask me what I want to do.", and during the first update, a checkbox should be provided asking the user if he wants automatic updates from then on.
My 2 cents.
LS
There is a fine line between being a cultivated citizen and being someone else's crop. - A. J. Patrick Liszkie
Fixing "memory hogging" generally require significant architecture changes. This is not the sort of thing you get on a x.x.x.1 release.
I'm sure they're addressing this issue as it is easily now the #1 complaint about Mozilla. I recall it having memory issues even before plugins and the memory-hogging history-full-page-store feature (the one where you hit "back" and the page is just supposed to pop up, not re-render or re-request), but those two issues have magnified the issue into something that can't be ignored or poo-poo'ed anymore; I, too, will often see my Firefox hovering around the 600MB mark, and I recently installed that memory leak test tool and it didn't come up often at all.
Probably ought to shut off that feature; doesn't seem to do much for me anyhow.