[Webkit-unassigned] [Bug 72808] Web Inspector: [Extensions API] Allow extensions to have their own "inspector" behavior

[bugzilla-daemon at webkit.org]

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





--- Comment #8 from Andrey Kosyakov <caseq at chromium.org>  2011-11-21 01:39:00 PST ---
(In reply to comment #7)

> Yeah, I have a list of things because of that. How do you uniquely identify elements for communication back and forth? Do you have a hidden id map?

We maintain a map between the ids used by the inspector and DOM nodes on the backend. We're wary of exposing an API to access the DOM model that we use in the front-end because it would be quite a complicated interface, potentially expensive to maintain. So at the moment the extensions that need DOM access need to use content scripts. You can probably implement your own marshalling of the DOM nodes to the inspector front-end extension pages, similar to the way it's done by the inspector.

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