news.yahoo.com— Mozilla today hit an early milestone on the road to the next version of its open-source browser, but the final product is still a year away, developers say.
Dec 10, 2006View in Crawl 4
I agree, 2.0 has turned me off to FF. I like all the add on's, and the customizability, but 2.0 has run slow for me. I still use FF from time to time, but I prefer Safari now
This is an alpha version of an upcoming version of Firefox. This does not mean that there will be no bugfixes for version 2.0. In fact, Mozilla supports the two most recent final versions of the Firefox browser with bugfixes and security updates. Right now, Mozilla supports Firefox 2.0 and Firefox 1.5. When v3.0 is released, they'll support Firefox 3.0 and Firefox 2.0
I'm running 3.0a1 on OS X 10.4.8 and it does not appear to pass the Acid2 test. Have the changes to the rendering engine been incorporated into Gran Paradiso yet? Or is this just somehow a Mac issue?
"if you're a good developer you shouldn't have compatibility issues" Well think about this... w3c is THE standard, browsers don't make standards, they either adhere to them or break them (like IE). Firefox 3 has had many advances in the way it renders CSS and such, so if you coded strictly to the w3c standards, the next version would FIX some things instead of breaking them...You should have one _proper_, w3c conforming CSS, and then have other CSS for hacks and fixes, that way you'll be removing fixes instead of constantly changing a CSS file.
The idea is that the gains outweigh the losses. Web developers should be writing to the web standards. If they are caught in the gray area between web standards and actual browser implementations, then they should sniff for browsers and send pages based on browser and version number, etc.
bbladesDec 10, 2006
I agree, 2.0 has turned me off to FF. I like all the add on's, and the customizability, but 2.0 has run slow for me. I still use FF from time to time, but I prefer Safari now
prattboyDec 11, 2006
This is an alpha version of an upcoming version of Firefox. This does not mean that there will be no bugfixes for version 2.0. In fact, Mozilla supports the two most recent final versions of the Firefox browser with bugfixes and security updates. Right now, Mozilla supports Firefox 2.0 and Firefox 1.5. When v3.0 is released, they'll support Firefox 3.0 and Firefox 2.0
prattboyDec 11, 2006
I'm running 3.0a1 on OS X 10.4.8 and it does not appear to pass the Acid2 test. Have the changes to the rendering engine been incorporated into Gran Paradiso yet? Or is this just somehow a Mac issue?
baddog121390Dec 11, 2006
opera>firefoxgo ahead, digg me down, you know it's true, even if your firefox fanboyism wont let you say it.
xilonDec 11, 2006
"if you're a good developer you shouldn't have compatibility issues" Well think about this... w3c is THE standard, browsers don't make standards, they either adhere to them or break them (like IE). Firefox 3 has had many advances in the way it renders CSS and such, so if you coded strictly to the w3c standards, the next version would FIX some things instead of breaking them...You should have one _proper_, w3c conforming CSS, and then have other CSS for hacks and fixes, that way you'll be removing fixes instead of constantly changing a CSS file.
norbiuDec 11, 2006
found some, nothing special yet.<a class="user" href="http://www.softpedia.com/progScreenshots/Mozilla-Firefox--FINAL-Screenshot-5787.html">http://www.softpedia.com/progScreenshots/Mozilla-Firefox--FINAL-Screenshot-5787.html</a>
leopardhunterDec 12, 2006
The idea is that the gains outweigh the losses. Web developers should be writing to the web standards. If they are caught in the gray area between web standards and actual browser implementations, then they should sniff for browsers and send pages based on browser and version number, etc.