Comments on: WebKit gets 100% on Acid3 http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/ There is a third way Tue, 08 Jul 2008 20:52:24 +0000 http://wordpress.org/?v=2.5.1 By: Epiphany using WebKit r32284 gets 100/100 (Acid3) « fbaldo http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7846 Epiphany using WebKit r32284 gets 100/100 (Acid3) « fbaldo Mon, 21 Apr 2008 07:59:39 +0000 http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7846 [...] 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 [...] [...] 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 [...]

]]> By: Alp Toker » Blog Archive » Acid3 final touches http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7832 Alp Toker » Blog Archive » Acid3 final touches Mon, 21 Apr 2008 02:38:41 +0000 http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7832 [...] 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 [...] [...] 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 [...]

]]> By: alp http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7382 alp Mon, 07 Apr 2008 02:41:06 +0000 http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7382 <b>Ashwin</b>: 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. 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.

]]> By: Ashwin http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7328 Ashwin Fri, 04 Apr 2008 19:52:53 +0000 http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7328 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? 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?

]]> By: Webkit完美通过Acid Test 3 | iLoveMac.cn http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7218 Webkit完美通过Acid Test 3 | iLoveMac.cn Mon, 31 Mar 2008 17:04:27 +0000 http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7218 [...] Build测试Acid Test 3的效果。得分100/100，完美通过！另外，Webkit的Gtk+移植版本（Epiphany）也接近于完全通过Acid Test [...] [...] Build测试Acid Test 3的效果。得分100/100，完美通过！另外，Webkit的Gtk+移植版本（Epiphany）也接近于完全通过Acid Test [...]

]]> By: WebKit achieves 100/100 in Acid3 public build! People continue to use Firefox. « Zayne Humphrey’s Blog. http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7154 WebKit achieves 100/100 in Acid3 public build! People continue to use Firefox. « Zayne Humphrey’s Blog. Sun, 30 Mar 2008 02:15:11 +0000 http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7154 [...] special bonus update: Alp Toker reports that the Gtk port now gets 100/100, although it does not yet match the reference [...] [...] special bonus update: Alp Toker reports that the Gtk port now gets 100/100, although it does not yet match the reference [...]

]]> By: LionsPhil http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7136 LionsPhil Sat, 29 Mar 2008 15:59:28 +0000 http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7136 Awesome work guys. Awesome work guys.

]]> By: alp http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7107 alp Fri, 28 Mar 2008 16:16:19 +0000 http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7107 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. 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.

]]> By: mwhenry.com » Blog Archive » What I’m Reading: 3/28 http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7105 mwhenry.com » Blog Archive » What I’m Reading: 3/28 Fri, 28 Mar 2008 15:41:32 +0000 http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7105 [...] 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. [...] [...] 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. [...]

]]> By: James Henstridge http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7092 James Henstridge Fri, 28 Mar 2008 06:46:42 +0000 http://www.atoker.com/blog/2008/03/27/webkit-gets-100-on-acid3/#comment-7092 Does it really count as 100% if you don't match the reference rendering? Does it really count as 100% if you don’t match the reference rendering?

]]>