[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 #4 from Steven Roussey <sroussey at gmail.com>  2011-11-20 11:57:50 PST ---
> Well, not really the own fork of the inspector - inspector uses native code for the highlight, while I am suggesting that you use CSS for your extension highlight.

Thus why I wanted some API to highlight. :) In Firebug we have several kinds. It looks like WI uses just one though. I prefer the kind that will conform to the shape of the outlined object, so I probably need my own. That's some work... ;)

> In either case, we don't expose DOM handles in the extensions API, so you would not be able to highlight the node you select.

I'm feeling dense, sorry. I don't know what you mean by that statement.

To create my own highlighter, I would:

1) Add to the WI status bar.
2) Inject code into user's page when the status bar button is hit. Will need to inject JS, and that JS can create DOM nodes and style sheets as needed.
3) listen for my panel being hidden, in which case i turn off highlighter, remove content from user's page, etc.
4) Code injected into user page adds DOM elements to block clicking which would also stop highlighter, removing DOM nodes, style sheets and JS objects.
5) While tracking the mouse in the user's content page, I need to send data on where the cursor is back to the background page and to the dev-tools page so that it can update info in WI.

Does this sound like the correct approach?

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