<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 11/30/2011 04:41 PM, Sebastian Heinlein wrote: <blockquote cite="mid:1322692907.4888.456.camel@klapprechner" type="cite"> <pre wrap="">Am Dienstag, den 29.11.2011, 20:27 -0500 schrieb Rodney Dawes: </pre> <blockquote type="cite"> <pre wrap="">On Tue, 2011-11-29 at 19:55 +0100, Sebastien Bacher wrote: </pre> <blockquote type="cite"> <pre wrap="">What is your take on using webkit 1.8? Is that choice good for other teams? Is there any issue or concern you have about updating? </pre> </blockquote> <pre wrap=""> As an aside, but also a valid issue, regardless of the version we go with… are there any sort of plans on getting Flash working inside the GTK3 version of webkit, out of the box? </pre> </blockquote> <pre wrap=""> "Thanks to the multiprocess architecture, WebKit2GTK+ solves the problem of using flash (or any other plugin using GTK+2) with GTK+3. The UI process depends unconditonally on GTK+3 and the plugin process is always built with GTK+2. And of course, flash will never crash or block your web browser. Plugins are broken in WebKitGTK+ 1.7.1 due to a bug that has already been fixed, so in order to try it out you need to either wait until 1.7.2 is released or build WebKit from current git master." <a class="moz-txt-link-freetext" href="http://blogs.igalia.com/carlosgc/2011/11/04/webkit2-gtk-minibrowser-ported-to-gtk-api/">http://blogs.igalia.com/carlosgc/2011/11/04/webkit2-gtk-minibrowser-ported-to-gtk-api/</a> </pre> <fieldset class="mimeAttachmentHeader"></fieldset> </blockquote> Right, but I thought WebKit2GTK+ was still going to be in beta for 1.8 which means that we probably wouldn't use it and it wouldn't solve any of our problems. Thanks, Micah </body> </html>