Slashdot Mirror
Firefox 3 RC1 Out Now
Jay writes "Firefox 3 Release Candidate 1 is out now. If yours didn't auto-update, then get it while it's hot! The release came a bit early, with Computer World noting: 'As recently as last Saturday, Mozilla's chief engineer said that although the company had locked down RC1's code, it was planning to publicly launch the build in "late May."'" My copy just downloaded — restarting after I save this story. God I hope it's better than the last beta.
Some changes are summarised here: http://mozillalinks.org/wp/2008/05/firefox-3-release-candidate-1-is-here/ . A new version of Cairo (1.6) is used under the hood.
For the last year, I have consistently seen on the Windows version an annoying bug. If one tab takes forever to load, any other tab will not load a new page either. I find Ebay is one of the worst to bring it out. If you switch to using IE in a tab, that tab will show about:blank.
I can understand some websites may make a Firefox tab crap out but it shouldn't affect the rest.
The issue I've seen with Flash isn't a crash, but that if one lingers on a page with a lot of Flash content (say, Youtube) and leaves the page up while browsing in other tabs, CPU eventually spikes to 99% usage, requiring the browser to be shut down.
Unfortunately, this isn't a Firefox problem, but a problem with the Flash plugin. The workaround I found (thanks to other Slashdot users) was to install the addon Flashblock. Now, instead of having the Flash content sitting and waiting, it's replaced by a little clickable object to load it. Since installing it, I have not experienced the CPU spike behavior, when it used to be a daily issue. Hope this helps folks.
RW
Comment removed based on user account deletion
http://www.squarefree.com/burningedge
Your comment leads me to believe you've never done any significant software development work. Consider that the Acid3 test was released at the tail end of the Gecko development cycle. This puts Mozilla in a bad position, because they were already at feature freeze and didn't want to further delay the final release. So, shooting for Acid3 compliance at this point would be the height of stupidity.
The Acid3 test is also a bit controversial in its own right. Acid1 and Acid2 addressed broad compatibility with several core web standards, without regard for any particular browser. In contrast, Acid3 covers an odd mix of quirks chosen to intentionally highlight bugs in different browsers. Acid3 also includes a random mix of features from things like SMIL and SVG, which are enormously complex standards not supported in their entirety by any major browser. That also means that Acid3 can be gamed by simply implementing just enough of a feature to pass the test, but not enough to be genuinely useful in practice.
Simply put, Acid3 is a much less useful test than the previous versions. I have no doubt that Mozilla will eventually pass, but they won't delay the Firefox 3.0 release and have made it clear that they won't play the partial implementation game to beat the test.