You are viewing extension docs in chrome via the 'file:' scheme: are you expecting to see local changes when you refresh? You'll need run chrome with --allow-file-access-from-files.
paramName
( optional enumerated Type array of paramType )
Undocumented.
Description of this parameter from the json schema.
This parameter was added in version . You must omit this parameter in earlier versions, and you may omit it in any version. If you require this parameter, the manifest key minimum_chrome_version can ensure that your extension won't be run in an earlier browser version.
Parameters

Google Chrome Extensions (Labs)

chrome.experimental.* APIs

chrome.experimental.* APIs

We'd like your feedback on the following experimental APIs:

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

How to use experimental APIs

  1. Make sure you're using the Dev channel of Google Chrome. Although the experimental APIs might work in other versions, we need your feedback on the latest incarnation of the APIs, which you can find on the Dev channel.
  2. Using the API documentation for the Dev channel, write the code for your extension.
  3. Specify the "experimental" permission in your extension's manifest, like this:
    "permissions": [
      "experimental",
      ...
    ],
    
  4. Specify the --enable-experimental-extension-apis flag when you launch the browser. On Windows, you can do this by modifying the properties of the shortcut that you use to launch Google Chrome. For example:
    path_to_chrome.exe --enable-experimental-extension-apis
  5. 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.