[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 #7 from Steven Roussey <sroussey at gmail.com>  2011-11-20 14:07:55 PST ---
> As I mentioned, we don't expose DOM handles in the extensions API: You can't highlight "nodes" in case you don't have "nodes" references / handles. Extensions extend the front-end, while nodes are running in the backend. We are using DOM node handles (WebInspector.DOMNodes) internally, but they are not exposed to the extensions.

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? xpath? And I will want to use some of the Element side panels as my own side panels (including a element hierarchy itself), which means I'll have to tell them what node to display, etc. These are things for down the road I guess, but it was nice to have them available in Firebug when I was developing Illuminations because I got what looked like big things working with little effort. It was motivating. I still have more to go, like showing the SASS/SCSS source as well as the CSS for frameworks that use them, like ExtJS and SpoutCore. But that obviously takes a lot longer than being able to reuse the Styles side panel right away. But this all seems like a digression. I suppose this bug should depend on another that exposes WebInspector.DOMNodes to extensions, and assuming that is not forthcoming, then I will pull in chunks of Firebu
 g to do the inspect/highlighter (and things like the Metrics side panel, etc). Or wait and see. I have a lot to do in the meantime.

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