Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 3.0 License, and code samples are licensed under the BSD License.
©2011 Google
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.
 |
- Getting Started
- Overview
- What's New?
Developer's Guide
- Browser UI
- Browser Interaction
- Implementation
- Finishing
Packaged Apps
Tutorials
Reference
- Formats
- Permission Warnings
- chrome.* APIs
- Other APIs
Samples
More
chrome.* APIs
chrome.* APIs
true
Google Chrome provides APIs such as
chrome.bookmarks and chrome.tab
so that extensions can interact with the browser.
Supported APIs
Here are the supported chrome.* APIs:
- bookmarks
- browserAction
- contextMenus
- cookies
- extension
- history
- i18n
- idle
- management
- omnibox
- pageAction
- tabs
- windows
Experimental APIs
Google Chrome also has experimental APIs, some of which will become supported APIs in future releases of Chrome.
API conventions
Unless the doc says otherwise, methods in the chrome.* APIs are asynchronous: they return immediately, without waiting for the operation to finish. If you need to know the outcome of an operation, then you pass a callback function into the method. For more information, watch this video: