Firefox 3.5 Hits Release Candidate Milestone

macupdate writes "Firefox 3.5rc1 has started trickling to users (mirrors and appropriate pages should all be updated soon). You can read the release notes. RC1 still scores a 93/100 on the Acid3 test."

Comments

v3.5 and still no MSI package for Windows

[denis-The-menace]

I wish Mozilla would make up their minds: are they going to target the Corps or not?

Even if you can get an MSI from Frontmotion (http://www.frontmotion.com/Firefox/download_firefox.htm), the corps will never go for it unless it comes off the Mozilla servers and is on the same web page as the current XPI installers. It's a "warm and fuzzy" thing that they need.

If Mozilla could somehow sanction those MSIs from Frontmotion then the corps would be more comfortable with it. Even a link from here (http://www.mozilla.com/en-US/firefox/all.html) would give FrontMotion's MSI package credibility.

Re:93/100...

[Phroggy]

Acid tests are designed to highlight rendering bugs in current browsers, giving browser developers a chance to easily see where something is going wrong. All major browsers currently pass Acid2, which means if you create a web page that only uses the kind of code that Acid2 tests for, you can be sure it will render precisely the same way in current versions of Firefox, Internet Explorer, Safari, Opera, Chrome, etc. This is a huge step forward; ten years ago, it wasn't uncommon for a page to work correctly in one browser but be completely unusable in another.

Now that all the major browsers pass Acid2, we need to find other ways in which web pages can display differently between different browsers. Since there is an official standard that defines what the correct behavior should be, we have something to test against; this is what Acid3 does. You're absolutely correct that passing Acid3 should not be the top priority, and failure to pass Acid3 is not a good reason for a user not to choose Firefox. However, the remaining things that prevent Firefox from passing Acid3 are indeed bugs, and eventually, they do need to be fixed. There are also other bugs in Firefox, that also need to be fixed, and many of these are more important than the bugs that cause Acid3 to fail.

I agree that HTML5 and CSS3 are awesome, but if browsers can't render them correctly, they're not much good. Acid tests are an incredibly useful tool for browser developers to ensure that this happens. Acid4 is already being planned, and will help to find bugs in the way browsers handle HTML5 and CSS3 and SVG and other stuff, taking into account some of the lessons learned from problems with the Acid3 test (for example, Acid3 tests rendering speed; Acid4 will not).