Acid Trip
There's been a lot of press recently, announcing the excellent support for the Acid 2 test. Since I've recently become a bit of a Web Implementation Enthusiast, I thought I'd see how the nascent Cairo WebKit implementation would do:
How about that? Even with all the code we have commented out of WebKit's Cairo version, it still achieves a perfect Acid2 score.
But what of Acid3? Perhaps unsurprisingly, it scores quite well -- 90/100. This is the same score as the main WebKit implementation. It's better than I would have expected, given that there are certainly several things that are not completely implemented in the Cairo back-end. However, these are apparently not important to the score of this particular test:
This is also a bit disingenuous; there is a font destruction problem that (depending on timing) causes the implementation to crash. But after loading the page a couple of times, I managed to get the test to run to completion. There's another bit of tomfoolery; this build of Cairo Webkit is still linking against Apple's proprietary CFNetwork. Once we cut over to the Curl back-end, this is certain to cause new woes.
But for today, we can chuckle smugly at IE 8 and its standards compliance.
How about that? Even with all the code we have commented out of WebKit's Cairo version, it still achieves a perfect Acid2 score.
But what of Acid3? Perhaps unsurprisingly, it scores quite well -- 90/100. This is the same score as the main WebKit implementation. It's better than I would have expected, given that there are certainly several things that are not completely implemented in the Cairo back-end. However, these are apparently not important to the score of this particular test:
This is also a bit disingenuous; there is a font destruction problem that (depending on timing) causes the implementation to crash. But after loading the page a couple of times, I managed to get the test to run to completion. There's another bit of tomfoolery; this build of Cairo Webkit is still linking against Apple's proprietary CFNetwork. Once we cut over to the Curl back-end, this is certain to cause new woes.
But for today, we can chuckle smugly at IE 8 and its standards compliance.
Comments