Acid3, make QtWebKit catch up
The Mac, Windows and Gtk+ port get 100/100 and pixel perfection for the acid3 test for quite a while but the Qt port was stuck somewhere else. How can this happen? For QtWebKit we decided to use as much of Qt as possible. So instead of relying on ICU we used the Qt Unicode support, instead of relying on libxml2 we used the QXmlStreamReader, instead of doing font matching and font/glyph caching we solely rely on QFont and QTextLayout to do the job. One had to apply some minor fixes to the Qt version of classes such as XMLTokenizer or TextCodec, or integrate SVGFonts into the Qt port as well...
What is next? We will have to get the rendering to be pixel perfect as well and then can merge the changes chunk by chunk. I'm going to sleep now, enjoy the screenshot.
posted by zecke @ 5:03 AM
7 Comments:
fantastic work!!!
Congratulations!
Awesome. Plugin support, Acid3,... those should make Qt 4.5 a very important release for QtWebKit. Hopefully the KHTML guys will realize that they should work with WebKit, not against it. *hoping for full WebKit support in Konqueror 4.2 or 4.3*
And then comes the stupid question.
About the disgusting and crappy and hated ... but necessary flash plugin.
Would it be possible to use the one of Safari, which should be better than the Linux version (you know, Adobe loooooooves Mac (and MacUsers love Adobe))?
Looks great! QtWebKit will just get better and better.
@temet: No. MacFlash (it is used in Firefox as well) isn't WebKit specific. It's OSX specific. You use the same Flash plug-in in WinIE, WinFirefox, WinSafari, WinKonqueror... You use the same flash in MacSafari, MacFirefox, MacKonqueror... You use the same flash in LinuxWebKit, LinuxKonqueror, LinuxFirefox... I hope Flash simply goes away someday!
WebKit passed Acid3 fully for the first time on Friday. So it's 100 subtests of 100 passed now.
Opera 9.60 Beta scored 85.
Post a Comment
<< Home