Mozilla’s Take on Acid3 Test
Posted in: Firefox 3, Mozilla, Opera, Software, Today's Chili, Web SitesThis article was written on April 02, 2008 by CyberNet.
For about a month now browser developers have been eyeing the new Acid3 test to see how they can push to meet the standards it tests for. Shortly after the test was released we took a look at how the browsers stacked up to each other, but none of them passed the test. Then just last week both Opera and Safari released test builds that demonstrate their compliance.
What about Firefox? Mozilla co-founder Mike Shaver wrote about his thoughts on Ian Hixie’s Acid3 test, and I think it’s safe to say that he’s not overly fond of it:
Ian’s Acid 3, unlike its predecessors, is not about establishing a baseline of useful web capabilities. It’s quite explicitly about making browser developers jump — Ian specifically sought out tests that were broken in WebKit, Opera, and Gecko, perhaps out of a twisted attempt at fairness. But the Acid tests shouldn’t be fair to browsers, they should be fair to the web; they should be based on how good the web will be as a platform if all browsers conform, not about how far any given browser has to stretch to get there.
Mike then went on to say how they won’t be getting support for the Acid3 test into the Firefox 3 browser, which is completely understandable. It’s very unlikely that Opera and Internet Explorer will be adding support Acid3 for their next major milestone releases either. And Safari just released a new version of their browser, and so their next milestone won’t exactly be soon. It’s obvious that the browser developers need time to test the necessary changes, and I don’t think anyone will criticize them for that.
Ian Hixie, one of the developers of the Acid 3 test, responded to Mike in the comments of his post. Here’s a snippet of what he had to say:
I would love to have tested innerHTML and setTimeout and all kinds of stuff like that, but sadly there is no spec for those yet (other than the very much in-progress HTML5 drafts). We can’t write Acid tests for things that we don’t have a spec for. I’ve been working my ass off for the past few years to write a spec for these things. Hopefully by, say, Acid5, we’ll be able to write an Acid test for them.
With Acid2, the original “first cut” failed a lot in IE, Mozilla, and Safari, but actually did pretty well in Opera. We (Håkon and I) then went on a hunt for Opera bugs and made Opera fare much worse on the test. With Acid3, IE and Opera ended up doing really badly on the first cut, and Firefox and Safari did well, so we added some more things that failed in Firefox and Safari. (Then we added even more stuff that failed in Safari, because they kept fixing the damn bugs as I was adding them to the test.)
Of course you wouldn’t want a bunch of the browsers to pass the test immediately after it is released because it wouldn’t really be doing any good. What are your thoughts about this?
[via ZDNet] Thanks to “Change” for the tip!
Copyright © 2010 CyberNet | CyberNet Forum | Learn Firefox
Related Posts:
- Browsers Start to Take Notice of Acid3 TestInternal Opera Build Passes Acid3 TestApple’s WebKit Scores 100/100 on Acid3, tooCyberNotes: Acid3 Browser ResultsRobots Invade Firefox 3… World Domination Next
In 
Last week 
We knew it was coming soon and it is finally here: 
If you use Firefox, I’m sure you have heard of Tab Mix Plus. When I setup computers for people this is always one extension that I install for them just so that they can harness the real power of Firefox. I mean really, those buttons that you see all over the place that say “Download Firefox with Google Toolbar” should really read “Download Firefox with Google Toolbar and Tab Mix Plus.” Nah, scratch that, it should just be included with Firefox.
This extension pretty much had its concept taken from the upcoming 
IE Tab brings the Website compatibility of Internet Explorer into Firefox. At the press of a button you can switch from a page being rendered by Firefox to it being rendered by Internet Explorer.
Okay, the first time I saw Tab Sidebar I just had to try it. If you have looked at the screenshot closely, you can already see how cool this is. This is a replacement to your tab bar and it will actually hide the tab bar when you make the sidebar visible.
This extension is for when you’re at work with people looking over your should you don’t want to have them see what tabs you have open. Page Title Eraser cures that problem by giving you the option to hide the title and icon on any tab. If you have multiple sites open there is an option available that will let you hide all the titles on all of your open tabs.
The concept of having a preview of a tab has become one of 
Colorful Tabs is nice because it makes finding certain tabs a little easier. When I have a bunch of tabs open it will sometimes start to look like one large tab with a horrid number of icons. I can find the site I am looking for 10 times quicker if I use this extension in conjunction with the Tab Preview one that I just mentioned.
Are you an Alt-Tab addict? This is the Alt-Tab option except for Firefox. Yep, you can shuffle through all your open tabs and see small previews by simply using the Ctrl-Tab keyboard combination.
This extension and Colorful Tabs have some similarities. The goal of Colorful Tabs is to make each tab stand out so that you can easily recognize different sites. Well, PageStyle2Tab actually makes it easier in my opinion. The color of the tab will match the style of the current page you are viewing. I am sure there are several sites that you visit that have a unique theme to them. Using this extension means you would be able to identify those sites even quicker.
Everyone loves to use thumbnails in extensions they create. The downside to Viamatic Tabnail is the fact that you must use up a large portion of your screen space. Actually, the size of the thumbnail is up to you which means the amount of space the extension uses is at your disposal.
