Bug 75366 - Web Inspector: [Extensions API] Method to open inspector at extension panel
Summary: Web Inspector: [Extensions API] Method to open inspector at extension panel
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-29 12:55 PST by Steven Roussey
Modified: 2014-12-12 14:36 PST (History)
11 users (show)

See Also:


Attachments
context menu example (3.80 KB, image/png)
2011-12-29 12:55 PST, Steven Roussey
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Steven Roussey 2011-12-29 12:55:56 PST
Created attachment 120766 [details]
context menu example

When you right click on an element there is an "Inspect Element" menu item to open the Inspector and bring you to that element in the Elements panel. Illumination does the same sort of thing, but tries to find the best match: ideally some sort of UI widget. But there doesn't seem to be a way to do this in Chrome, etc., like I can in Firefox/Firebug (see example context menu screenshot attached).
Comment 1 Steven Roussey 2011-12-30 09:51:50 PST
I should be clear as to what's needed: an api to open the web inspector and switch to a desired panel (giving that panel information to focus on could be done in a callback when the main method is complete).
Comment 2 Pavel Feldman 2012-01-04 06:05:55 PST
This seems to be a platform-specific request, so it should start in crbug.com.

In either case, we avoid opening the front-end programmatically for the following reasons:
- It increases API surface that can be used by malicious sites / extensions
- It increases the risk of the extensions API mis-use where a regular extension (say ad block) might use powerful inspector API via opening the front-end and installing a hook into the page.

both scenarios are bad for the users.
Comment 3 Brian Burg 2014-12-12 14:36:16 PST
Closing as invalid, as this bug pertains to the old inspector UI and/or its tests.
Please file a new bug (https://www.webkit.org/new-inspector-bug) if the bug/feature/issue is still relevant to WebKit trunk.