[Webkit-unassigned] [Bug 105631] [GTK] Add support for loading web process extensions

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Dec 31 07:08:44 PST 2012


https://bugs.webkit.org/show_bug.cgi?id=105631





--- Comment #9 from Carlos Garcia Campos <cgarcia at igalia.com>  2012-12-31 07:10:46 PST ---
(In reply to comment #8)
> (In reply to comment #7)
> > (In reply to comment #6)
> > > I see this kind of uses the InjectedBundle, but also kind of doesn't (you have extra code in WebProcessSoup).  Why can't this all be done on top of the InjectedBundle mechanism and the WebKit2 API?
> > 
> > This is just a first patch, we will use the injected bundle C API to implement things like bug #79918 and bug #99695. But instead of allowing apps to install their own injected bundle we use a builtin injected bundle, like qt does as well, to implement a web extensions system. This also allows us to expose the GObject DOM bindings API we use in WebKit1. And as we do for the UI process we expose our custom high level GTK+ API for the web process instead of the C API one.
> 
> That doesn't exactly answer why you need to change WebProcessSoup?

Yes, to create the builtin injected bundle when the UI process hasn't passed a injected bundle path (typically WTR). This is what qt does too, see WebProcessQt.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list