Webkit had to request changes to the tests in in Acid2.
The Wikipedia page mentions that Acid3 was also updated to match Firefox's change in behavior:
"On 2 April 2010, Ian Hickson made minor changes to the test after Mozilla, due to privacy concerns, altered the way Gecko handles the :visited pseudo-class."
There's http://html5test.com/ (which is only so-so as a test, since last I checked it only tests whether a feature is feature-detectable, not whether it actually _works_ or anything, for the most part; see the "input element types" section in Safari 5, say).
Once IE is passing Acid3 or close to it, Hixie was going to consider working on Acid4, maybe.
Note, by the way, that most of the point of the Acid2/3 tests is not to push new functionality as much as to push correct implementation of _old_ functionality: stuff that's been specced for a while but is buggily implemented. This was less true of Acid3 than Acid2; last I heard the plan was for Acid4 to be more like Acid2 in this regard.
So are you really looking for new stuff, or correctly implemented stuff? ;)
The article does not sound like that at all. There is not even a hint of the assertion that the browsers that do implement part of the SVG spec only did so in order to game the acid test.
It may remind you of such affairs, but people are likely to come away from your comment with a wrong impression of the article.
> I wrote this post since there isn’t a highly ranked piece on this if you search for “Firefox Acid3,” and there should be. Hopefully my site’s search engine ranking can be useful for something.
Am I missing something? Is his site supposed to have great google mojo? I ran the search he specified, as well as several variants, and couldn't find him in the first 12 pages. OTOH, Wikipedia's article on Acid3 [1], which is Google's first result, makes much the same point as he does. In fact, it cites him, which is probably a bad thing, given it's a blog.
Has anybody used SVG fonts on the Web? I'm curious.
I realize that there's a bit of a chicken-and-egg problem with browsers not supporting it, but it seems to me that the really good features start picking up traction even when only a few browsers support it (e.g. CSS transitions and animations, the latter of which Firefox still doesn't support).
If you wanted webfonts on iOS versions before 4, you had to use SVG fonts on that platform. They weren't great though, and having the choice to use TTF/OTF now is much better.
Uh... did you read the article? Did you read Robert O'Callahan's blog post it links to?
We sure can implement a broken version of SVG Fonts just to pass Acid3. We think doing that is 1) unethical and 2) bad for the web. So we're not going to do that.
It's not a technical difficulty. It's pointless, because WOFF does everything SVG fonts do, but is actually supported by font foundries and the Web in general.
