Bug 31508 - Need support for 'isolated worlds' concepts on the API
Summary: Need support for 'isolated worlds' concepts on the API
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC All
: P2 Normal
Assignee: Nobody
URL:
Keywords: Gtk, LayoutTestFailure
Depends on:
Blocks:
 
Reported: 2009-11-14 06:05 PST by Gustavo Noronha (kov)
Modified: 2014-04-08 18:26 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gustavo Noronha (kov) 2009-11-14 06:05:24 PST 
Revision 50973 added this test, and some infrastructure to all ports. We may need to implement something similar to what Mac/Win have in DRT, and also perform the same changes they did in FrameLoaderClient.
Comment 1 Gustavo Noronha (kov) 2009-11-15 07:11:25 PST 
So, from my quick investigation, isolated worlds looks very much like what we were looking for when we were talking about using seed to do javascript inside WebKit - it is meant to isolate the global contexts, and allow specific contexts to have a bigger privilege. We will need to add API to deal with worlds - JSC doesn't deal with them, they are a WebCore concept, and we will have to extend our window-object-cleared signal to also give a World object (we'll need to have a wrapper here).
Comment 2 Zan Dobersek 2011-11-06 06:53:27 PST 
Is there still any interest for this API?
Comment 3 Martin Robinson 2014-04-08 18:26:16 PDT 
We have WebKitScriptWorld in the WebKit2 injected bundle API now.