Bug 33047 - [V8] Use ScriptState instead of accessing v8::Context directly
Summary: [V8] Use ScriptState instead of accessing v8::Context directly
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 33016
Blocks:
  Show dependency tree / graph
 
Reported: 2009-12-30 03:33 PST by Yury Semikhatsky
Modified: 2014-12-16 00:48 PST (History)
2 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 Yury Semikhatsky 2009-12-30 03:33:37 PST 
ScriptState is an abstraction of JavaScript VM execution state that works for both V8 and JSC. When possible WebCore code should manipulate this abstraction instead of using v8::Context directly. The ScriptState instance can be retrieved from ScriptController(for main isolated world) or from V8IsolatedWorld.
Comment 1 Adam Barth 2009-12-30 14:04:38 PST 
Note that V8IsolatedWorld is going to lose its ScriptState soon to more closely match how JSC does things.
Comment 2 Brian Burg 2014-12-16 00:48:27 PST 
Closing some V8-related work items.