experimental.webInspector.* APIs

Contents

1. h2Name
   1. h3Name
2. API reference
   1. Properties
      1. propertyName
   2. Methods
      1. methodName
   3. Events
      1. eventName
   4. Types
      1. id

The following API modules provide support for extending Chrome Development Tools (aka WebInspector):

• experimental.webInspector.audits
• experimental.webInspector.inspectedWindow
• experimental.webInspector.panels
• experimental.webInspector.resources

Caution: Don't depend on these experimental APIs. They might disappear, and they will change. Also, the Chrome Developer Dashboard doesn't allow you to upload extensions that use experimental APIs.

How to use WebInspector APIs

1. WebInspector APIs are currently experimental, so please start with the steps for using experimental extension APIs.
2. Specify the "devtools_page" field in your extension's manifest and make sure you have "experimental" permission:

   {
     "name": ...
     "version": "1.0",
     "minimum_chrome_version": "10.0",
     "devtools_page": "devtools.html",
     "permissions": [ "experimental" ... ],
     ...
   }
   

3. An instance of the devtools_page specified in your extension's manifest will be created for every Developer Tools window opened. The page may add other extension pages as panels and sidebars to the Developer Tools window using experimental.webInspector.panels API.
4. The APIs available to extension pages within the Developer Tools window include all experimental.webInspector modules listed above and chrome.extension API. Other extension APIs are not available to the Developer Tools pages, but you may invoke them by sending a request to the background page of your extension, similarly to how it's done in the content scripts.
5. Please note that, unlike other Chrome Extension APIs, the WebInspector APIs lack "chrome" prefix. This is because the APIs, as the WebInspector itself, are a part of WebKit and may eventually appear in other browsers.
6. Give us feedback! Your comments and suggestions help us improve the APIs and decide which ones should move from experimental to supported.

More information

For information on the standard APIs that extensions can use, see chrome.* APIs and Other APIs.