diff options
Diffstat (limited to 'chrome/common/extensions/docs/static/debugger.html')
| -rw-r--r-- | chrome/common/extensions/docs/static/debugger.html | 45 |
1 files changed, 45 insertions, 0 deletions
diff --git a/chrome/common/extensions/docs/static/debugger.html b/chrome/common/extensions/docs/static/debugger.html new file mode 100644 index 0000000..433d2a0 --- /dev/null +++ b/chrome/common/extensions/docs/static/debugger.html @@ -0,0 +1,45 @@ +<!-- BEGIN AUTHORED CONTENT --> + +<h2 id="manifest">Notes</h2> + +<p> +Debugger API serves as an alternate transport for Chrome's +<a href="http://code.google.com/chrome/devtools/docs/remote-debugging.html"> +remote debugging protocol</a>. Use <code>chrome.debugger</code> +to attach to one or more tabs to instrument network interaction, debug +JavaScript, mutate the DOM and CSS, etc. Use the Debuggee tabId to target tabs +with sendCommand and route events by <code>tabId</code> from onEvent callbacks. +</p> + +<p> +As of today, attaching to the tab by means of the debugger API +and using embedded Chrome DevTools with that tab are mutually exclusive. +If user invokes Chrome DevTools while extension is attached to the tab, +debugging session is terminated. Extension can re-establish it later. +</p> + +<h2 id="manifest">Manifest</h2> + +<p> +You must declare the "debugger" permission in your extension's manifest +to use this API. +</p> + +<pre>{ + "name": "My extension", + ... +<b> "permissions": [ + "debugger", + ]</b>, + ... +}</pre> + + +<h2 id="examples">Examples</h2> + +<p> +You can find samples of this API in +<a href="samples.html#debugger">Samples</a>. +</p> + +<!-- END AUTHORED CONTENT --> |