[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 #6 from Pavel Feldman <pfeldman at chromium.org>  2010-04-09 11:32:26 PST ---
> 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.
> 

We try to avoid using isolated worlds since they require management and eat
heap. Management part turned out to be inevitable, but the memory one we could
save by means of injected script that we anyway need for main world inspection.

> 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).

I agree with the general idea. Unfortunately, it is not always possible. Like
for styles inspection of iframes loaded cross domain, we needed to move to
native. Creating node wrappers can also be expensive and affect GC, etc. So
yes, we are for simplicity, but we are first of all for accuracy.

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