blob: 433d2a0e1bb992bc1bd561cdc0569a0007d48c67 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
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 -->
|
