Loading ...Third Firefox 3 RC to fix critical Mac OS X bug
Published: June 10th, 2008
Mozilla developers decided today to spin a third Firefox 3 release candidate to ensure the next major update will meet users’ stability expectations.
This time, the showstopper was identified and reported last week on Mac OS X versions of Firefox 3 RC 2. The bug causes Firefox to hangwhen loading the plugin database in some special conditions on Mac OS X 10.5.3, the latest Mac OS X update released on May 28. I was unlucky enough to hit it so I, for one, appreciate the attention to this bug that is also present in Firefox 2.0.0.14.
The bug has been fixed and is already available in the latest RC3 builds. Windows and Linux users will get the exact same RC 2 build.
Despite the delay, Firefox 3 release is still targeted for June.
You can leave a response, or trackback from your own site.
Subscribe RSS
Subscribe email
June 11th, 2008 at 5:10 pm
There are still critical flaws. Every time i launch Fx in OS X 10.5.3, Fx is minimized to the upper left. it’s about 1″ by 1″. Good to see that there is progress though :). Fx 3 is awesome.
[Reply]
June 12th, 2008 at 5:47 pm
I upgraded yesterday my iMac to Leopard and today I decided to test the RC3 of Firefox, as I use ONLY Firefox 2 and never Safari.
Unfortunately when RC3 replaced Firefox 2, it imported the almost unused Safari’s bookmarks, without asking me if I would like that. BTW I think I’ve lost 2 years of Safari 2 bookmarks.
-Does Anybody knows if is there a security copy located somewhere?
-How this tremendous bug can be put as a NEW version of the most used non MS browser, on next week?
-Why Firefox 3 RC3 does NOT ask if you want to import bookmarks?
[Reply]
Gerson Braschi BRAZILJune 12th, 2008 at 6:01 pm
After the “accident” above, I stopped using Fx3rc3 and started using Safari and discovered, right now, that as a result of the upgrade from Tiger to Leopard, yesterday, during the installation, Safari 3.1.1 IMPORTED ALL MY 2 YEARS BOOKMARKS FROM FIREFOX 2.
Thanks to Apple Safari.
[Reply]