WebKit HTML5 canvas enhancements, Acid2 support and more
Improved WebKit HTML5 canvas support
Brent Fulgham has been merging Cairo graphics backend features from the Adobe Apollo/AIR branch of WebKit (#16558, #16577, #15382). The Adobe developers have been cooperative and their code is well-written — hopefully they’ll start merging their own work soon. This puts the graphics backend a couple of weeks ahead of schedule (the original target was GNOME 2.24):
Acid2
Luca Bruno has provided the last (#16365) in a series of fixes to get the Acid2 smiley face rendering correctly. This should help dispel rumours that the WebKit/GTK+ team is dropping acid.
Image decoder enhancements
Google engineers have contributed a handful of improvements (#15974, #16169) to WebKit’s image decoders, which will be shared between the GTK+ and Android ports.
Mobile features designed for Android can also now be easily enabled in the GTK+ port (eg. LOW_BANDWIDTH_DISPLAY support, r28960). It’s great to see cooperation on features like this.
Trunk open for Maemo/Hildon
The Maemo/Hildon mobile platform (used in Nokia internet tablets and Ubuntu Mobile) is now an official component of the GTK+ port. This means that these libraries can be used directly in WebKit instead of being maintained out of tree.
The JavaScript engine has seen recent optimizations which bring it further ahead of the stock browser shipped in OS2008 for the N800/N810 devices. Check out any of the freely available JS/AJAX benchmarks if you’re interested in performance.
GtkPrint
Initial printing support (#15576) has landed. Cairo’s paginated surface API lacks some features we need to implement this fully. I’ve posted a proposal for new API that will be useful in matching the print functionality of the Mac and Win ports.
Very cool. I’m really excited about being able to run Epiphany with Webkit/GTK in the not too distant future. Rock on!
[…] ciclo de desarrollo basado en betas permite que nosotros, los usuarios, podamos disfrutar de estas nuevas características en el momento en el que se desarrollan, de ahí que seamos nosotros los encargados en testear la […]
Is anyone packaging this for 770/800? URL?
Wondering: Development of WebKit EAL was happening at http://git.collabora.co.uk/ but the repository was pulled recently. EAL was an awkward abstraction for modern browser engines like WebKit so this isn’t a big deal.
A couple of WebKit/GTK+ developers will be looking into putting together a standalone reference WebKit browser for Maemo complete with nightly builds in the next few weeks. Help from the Maemo developer community will be welcome since this is an unofficial project.
I hope we can bring development out into the open after a year of screenshot-only blog posts and source-code-only releases.
Hi Alp,
rocking news. Totally 😉 Thanks a lot for all your efforts.
/me waiting for the day when most of the gnome stack has a single excellent HTML widget and not gecko, gtkhtml3, gtkhtml etc 😉
Hey Alp,
what is that starred background you’re using on that screenshot? I love stars 🙂
Oh, and congratulations on the great work you’re doing on webkit/gtk!
[…] gets Native getElementsByClassName and does ACID2. w00t! Spread the […]
“This should help dispel rumours that the WebKit/GTK+ team is dropping acid.”
…hey if it worked for the developers of early microprocessors there’s nothing to be ashamed of… 🙂
[…] adding support for the getElementsByClassName JavaScript function, beginning to add support for HTML 5, creating a new JavaScript benchmark called SunSpider and getting ready for its big Qt 4.4 and GTK […]
Rui: Man, I love this background. Don’t know how long I’ve had it. I couldn’t find the original source so I’ve put it up for you to download:
http://www.atoker.com/tmp/OTHER-BluelightStar_1400x1050.png
Just a short note to say that the Cairo-backed Windows build of WebKit use those image decoders as well!