1. Multimedia in
Past / Present / Future
Philippe Normand, Igalia
2. About WebKit itself
IT IS NOT A BROWSER, it is a framework to build
Fork of KHTML started by Apple, now with
contributors all over the place.
Shared base, with ports being built from the
same tree, with different build systems.
No stable API, no API documentation
Each port provides its own API
3. What is WebKitGTK+?
a WebKit port providing a GTK+ friendly API
A regular GtkWidget which you can add to your
Rendering backend built with Cairo.
Resource loading backend built with libsoup.
Pango for fonts
Keyring for auth storage
GStreamer for audio/video
4. Multimedia in WebKit
3 layers from top to bottom:
graphics: cross-platform MediaPlayer bridge
platform-specific MediaPlayerPrivate backend
In the GTK+ port: video painting on a Cairo
surface, buffers retrieved from a custom video
5. Until September 2009
36% Skipped media tests, out of 97 (flaky or
Not really useful without controls UI.
Demo from the past
6. Since September 2009
Only 23% Skipped media tests (out of 108)!
Simple controls UI (initial patch by Zan
Trick modes (reverse playback, ffwd playback)
QuickTime ref movies: redirections
Better integration with PulseAudio
data: uris support (upstreamed to gst-plugins-
on-disk buffering (review in progress)
WebKit src element (patch by Sebastian Dröge)
7. Youtube and HTML5
8. Oh, and Vimeo too!
9. Work in progress
More media tests fixing
Fullscreen video display
(Web)MediaPlayer (can be used for things like
#webkit and #webkit-gtk on irc.freenode.org
webkit-gtk and webkit-dev mailing lists at