Rearchitecting the Web Inspector

The main goal here is to divorce the web inspector from having direct access to any objects on the page. This will allow for moving the inspector into it's own process (required for Chromium), but also to increase confidence of security (e.g. JSWrapper objects should no longer be needed).

The long-term goal is to have a well-defined API that speaks JSON between the Inspector's JS and the underlying representation of the page. At first, that underlying representation of the page will be written entirely in JS and access the inspected page's DOM directly. Eventually, we can start moving appropriate bits to C++, or in Chromium's case IPC, as necessary.

APIs to implement

We'll put all these as objects on the InspectorController.

Console

InspectorController.Console

Profiler

InspectorController.Profiler

Resources

InspectorController.Resources

DOM

InspectorController.DOM.getChildren(node) InspectorController.DOM.getParent(node)

node here is a JS object that has a one-to-one mapping with the DOM node in the page. E

Database

Debugger

Miscellaneous other notes