wiki:ProposedWebInspectorRearchitecting

Version 3 (modified by ojan@chromium.org, 14 years ago) (diff)

--

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.

The eventual stack will look something like this:

Inspector JS


API Shim JS


InspectorController C++ Give this a generic client (InspectorControllerClient?) that Chromium can implement as IPC.


Possibly an IPC layer


C++ Receives calls from the InspectorControllerClient


Inspected Page's JS

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. Everything above this API layer only knows about the node JS object. Somewhere in the implementation of the API there needs to be a mapping. Initially, it can just be an in JS map. Eventually, the map will probably move to C++, at the very least it will for the IPC-based version.

Database

InspectorController.Database.getCurrentStack() ?

InspectorConteoller.Database.?

Debugger

InspectorController.Debugger.?

Miscellaneous other notes

Objects viewed in the console should be snapshots (i.e. not live). In addition to matching user expectations better, this means we don't need to worry about objects on the page getting GCed. Similarly, any live objects in the debugger should not be GCable.

For making sure the inspector has zero impact on page load times and minimal impact on memory usage we agreed on a few UI changes. Network monitoring and possibly debugging should be opt-in per-site. The console should only keep around XXX messages unless the user opts-in to keep more (all?) messages for that site. Currently, Chromium has XXX==100, but that was a relatively arbitrary decision. As a side note, the Chromium/V8 debugger is already zero cost until a debug statement is actually hit, so Chromium doesn't actually care about the debugger being opt-in.