[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 #4 from Pavel Feldman <pfeldman at chromium.org>  2010-04-09 08:27:53 PST ---
> I don't see how Value helps at all with the drawbacks you mention.  Is the goal
> to not have to run any JavaScript on the inspected page at all?  For some
> areas, like DOM interaction, JavaScript seems like a great way to write the
> code running on debug target; for other areas, like JavaScript debugging, it
> makes no sense (there are no public JS debug APIs).
>

Nope, this is not related to the injected scripts and running js in the
inspected page. It is about not using inspected page javascript engine for the
transport.

> I'm not against using Value at all, it looks rather nice.  I just don't
> understand how it addresses the drawbacks you mention.
> 
> It seems like using isolated worlds to implement things like the DOM
> introspection kit running in the debug target would help with some of the
> drawbacks you mention (allowing you to separate profiling/debug/gc/etc user
> code from debug code accessing the same DOM).

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.

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

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