Bug 33047
| Summary: | [V8] Use ScriptState instead of accessing v8::Context directly | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Yury Semikhatsky <yurys> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | abarth, dglazkov |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | 33016 | ||
| Bug Blocks: | |||
Yury Semikhatsky
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Adam Barth
Note that V8IsolatedWorld is going to lose its ScriptState soon to more closely match how JSC does things.
Brian Burg
Closing some V8-related work items.