ArsTechnica have posted an in-depth look at Mozilla's new project, Firefox 3.0. The significant jump from 2.0, released a mere 2 months ago is mainly due to Mozilla's use of the new Gecko rendering engine.
Mozilla has officially released the first public alpha build of Firefox 3.0. Codenamed Gran Paradiso, Firefox 3 includes the new Gecko 1.9 rendering engine which leverages the open-source Cairo rendering framework and features heavily re factored re flow algorithms that improve Firefox layout functionality and resolve some long-standing CSS bugs.
The re flow improvements in Gecko 1.9 (included in the latest Gran Paradiso nightly build, but not the alpha release) finally enable Firefox to pass the Acid 2 test, a CSS test case developed by the Web Standards Project to illuminate flaws in HTML/CSS rendering engines. To pass the Acid 2 test, browsers must comply with W3C standards and provide support for a wide variety of features that are considered relevant by Web designers. The Acid 2 test has been passed by several other browsers, including Safari, Konqueror, and Opera, but not Internet Explorer. Passing Acid 2 is considered to be a significant milestone in Firefox development.
Download: Mozilla 3.0 Nightly Alpha builds! Mozilla recommends staying with FF2
View: Full Article @ Ars.
Link to: Neowin Discussion
Mozilla has officially released the first public alpha build of Firefox 3.0. Codenamed Gran Paradiso, Firefox 3 includes the new Gecko 1.9 rendering engine which leverages the open-source Cairo rendering framework and features heavily re factored re flow algorithms that improve Firefox layout functionality and resolve some long-standing CSS bugs.
The re flow improvements in Gecko 1.9 (included in the latest Gran Paradiso nightly build, but not the alpha release) finally enable Firefox to pass the Acid 2 test, a CSS test case developed by the Web Standards Project to illuminate flaws in HTML/CSS rendering engines. To pass the Acid 2 test, browsers must comply with W3C standards and provide support for a wide variety of features that are considered relevant by Web designers. The Acid 2 test has been passed by several other browsers, including Safari, Konqueror, and Opera, but not Internet Explorer. Passing Acid 2 is considered to be a significant milestone in Firefox development.
















A Developer Preview is also an alpha version of a new project, it's also mentioned on the Mozilla Website.
The filename also suggests alpha firefox-3.0a1.en-US.win32.installer.exe (Alpha 1)
Sure sounds like Alpha 1 to me
Last edited by Skyfrog on 13 Dec 2006 - 15:07
I use it in both Windows and Linux. It seems pretty much the same to me in either.
How about that linux troll?
Last edited by Skyfrog on 13 Dec 2006 - 15:06
Why? If IE was to strictly conform to the web standards needed to pass Acid 2, millions (and perhaps billions) of websites across the web would break over night.
The pathetically small changes they made in IE7 already broke a few million web pages, and that was only inching towards conforming to web standards in any vague sense.
It's the curse of being that big and that popular (still roughly 90% of the market)...you can't possibly make any drastic changes without the s**t hitting the fan.
I forgot where I read it, but the article said the Firefox 3.0 a1 nightlies did past Acid Test 2.
I'm sure if they made IE only be strict with XHTML doctypes, all would be fine. AFAIK, IE6 doesn't even recognise XHTML doctypes. I don't know what IE7 does.
In fact, this would be the best thing they could do. All the newbie pages can be in HTML 4 and rendered with IE's convoluted rendering engine, while anyone who knows what they are doing and want their page to look the same across every browser can use the stricter XHTML.
Last edited by AfroTrance on 14 Dec 2006 - 07:55
I'm sure if they made IE only be strict with XHTML doctypes, all would be fine. AFAIK, IE6 doesn't even recognise XHTML doctypes. I don't know what IE7 does.
In fact, this would be the best thing they could do. All the newbie pages can be in HTML 4 and rendered with IE's convoluted rendering engine, while anyone who knows what they are doing and want their page to look the same across every browser can use the stricter XHTML.
They've been doing that since IE6.
http://msdn.microsoft.com/library/default....nhancements.asp
Is it perfect? No, but the ground work is there.
Is it just me or do the fonts on webpages look cleaner? And neowin looks really clean with it?
Most of the features that will end up in v3 aren't in there yet. Places for example hasn't been added in yet. Basically at this point the rendering engine is the only obvious difference.
[Update] *snip* ignore this. I figured out it has nothing to do with Firefox 3
Last edited by xxdesmus on 13 Dec 2006 - 22:32
Can't wait for final release.
huh?
But then again, I probably won't try Firefox 3 until Beta 1 comes out as with any other Firefox release.
Our firefall actually doesnt allow Firefox!!...simply because, it FAILED in lot of security related functinalities...
(And our senior IT consultants says MS will provide a patch if anything is site on...but we cannot urge similar things (providing a patch) from any opensource partner...
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.