WebKit gets 100% on Acid3
Today we reached a milestone with WebKit/GTK+ as it became the first browser engine on Linux/X11 to get a full score on Acid3, shortly after the Acid3 pass by WebKit for Safari/Mac.
There is actually still a little work to be done before we can claim a flawless Acid3 pass. Two of the most visible remaining issues in the GTK+ port are :visited (causing the “LINKTEST FAILED” notice in the screenshot) and the lack of CSS text shadow support in the Cairo/text backend which is needed to match the reference rendering.
It’s amazing to see how far we’ve come in the last few months, and great to see the WebKit GTK+ team now playing an active role in the direction of WebCore as WebKit continues to build momentum amongst developers.
Update: We now also match the reference rendering.

March 27th, 2008 at 11:03 pm
Amazing !
March 27th, 2008 at 11:24 pm
Lack of support for :visited seems like a feature.
March 27th, 2008 at 11:34 pm
How long until us mere mortals can install a .deb of epiphany-webkit in Hardy?
I can’t wait
March 27th, 2008 at 11:53 pm
Awesome. There’s just one thing I miss: some debian or ubuntu repository with updated packages of webkit nightlies and browsers using it (Epiphany, Juniper, Midori, maybe some else)…
March 28th, 2008 at 12:24 am
[…] special bonus update: Alp Toker reports that the Gtk port now gets 100/100, although it does not yet match the reference […]
March 28th, 2008 at 12:48 am
Yeah, “:visited” is so annoying …
March 28th, 2008 at 7:46 am
Does it really count as 100% if you don’t match the reference rendering?
March 28th, 2008 at 4:41 pm
[…] WebKit gets 100% on Acid3: “Yesterday’s news” you say? Nope. The news today is about Webkit/GTK. Awesome news for us LXers. Also, definitely take a look at this account of the main Webkit team’s road to 100/100. It’s got some fun insights for spectators of the race between Webkit and Opera for full Acid3 compliance. And for some (probably much-needed) perspective, here’s one Mozilla-er’s take on the Acid3 arms race. […]
March 28th, 2008 at 5:16 pm
jamesh: 100/100 of the tests really do pass, but like I explained there are still some things to be done to achieve a flawless pass such as matching the reference rendering — which isn’t tested automatically and so not part of the the 100 groups of core tests.
Some of these fixes need to be done by the GTK+ porting team, and one or two directly in WebCore. They are mostly minor tweaks that should get done over the next few days.
March 29th, 2008 at 4:59 pm
Awesome work guys.
March 30th, 2008 at 2:15 am
[…] special bonus update: Alp Toker reports that the Gtk port now gets 100/100, although it does not yet match the reference […]
March 31st, 2008 at 6:04 pm
[…] Build测试Acid Test 3的效果。得分100/100,完美通过!另外,Webkit的Gtk+移植版本(Epiphany)也接近于完全通过Acid Test […]
April 4th, 2008 at 8:52 pm
I can’t even compile it with svg enabled! Wondering how it passes?
./configure –enable-video –enable-svg –prefix=/opt/socialtv
make
DerivedSources/SVGElementFactory.cpp: In function ‘WebCore::SVGElement* WebCore::altGlyphConstructor(WebCore::Document*, bool)’:
DerivedSources/SVGElementFactory.cpp:129: error: expected type-specifier before ‘SVGAltGlyphElement’
DerivedSources/SVGElementFactory.cpp:129: error: cannot convert ‘int*’ to ‘WebCore::SVGElement*’ in return
DerivedSources/SVGElementFactory.cpp:129: error: expected ‘;’ before ‘SVGAltGlyphElement’
DerivedSources/SVGElementFactory.cpp:129: error: ‘SVGAltGlyphElement’ was not declared in this scope
…
Any clue?
April 7th, 2008 at 3:41 am
Ashwin: Try –enable-svg-experimental instead. Looks like the standard –enable-svg is busted. You’ll need to clean your build tree from the previous attempt.
We’ll need to move some SVG features from the experimental profile to the stable one now that they’re becoming mature and interdependent.
April 21st, 2008 at 3:38 am
[…] we’ve been working to finish off and land the last couple of fixes to get a perfect pixel-for-pixel match against the reference Acid3 rendering in WebKit/GTK+. I […]
April 21st, 2008 at 8:59 am
[…] in OS, sw Epiphany using WebKit r32284 gets 100/100 (Acid3). Recently we’ve been working to finish off and land the last couple of fixes to get a perfect […]