[Webkit-unassigned] [Bug 37306] Web Inspector: Stop using JavaScript Script* objects as a transport for InspectorController <=> front-end interaction.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=37306





--- Comment #5 from Patrick Mueller <pmuellr at yahoo.com>  2010-04-09 08:52:00 PST ---
(In reply to comment #4)
> Although unrelated to this bug, you can't use isolated world for inspecting dom
> - you want to inspect dom wrapper properties belonging to the main world.

Ah yes.  Though of course you can introspect over the DOM, just can't see
anything the main world tacked on to it.  Of course we need to see those bits
the main world tacked on for Web Inspector.  Of course, there are layers here. 
For initial element tree population, for example, you can get by with stuff
that's is available to the isolated world.

A better example would be DOMStorage, which you could presumably access via an
isolated world. A trivial amount of diagnostic information on app-cache (ie,
the current public API on app-cache) would also likely be obtainable via an
isolated world.

> > I don't see "introduces
> > artificial js environment" as a big drawback :-)
> 
> That's because you don't have to maintain page inspection within existing and
> improving security constraints. Calling js between contexts is considered
> harmful.

Which is why isolated worlds are so great.

The whole reason I'm bringing this up is that I'd like to see as much of Web
Inspector written in JS as is possible/reasonable.  Like it is today, only
more.  Not less.  It's not clear to me whether this bug affects that or not,
and if it does, affects it negatively (more C++ code) or positively (more JS
code).

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.