| OLD | NEW |
| (Empty) |
| 1 <!-- BEGIN AUTHORED CONTENT --> | |
| 2 <h2 id="manifest">Notes</h2> | |
| 3 <p> | |
| 4 Debugger API serves as an alternate transport for Chrome's | |
| 5 <a href="http://code.google.com/chrome/devtools/docs/remote-debugging.html"> | |
| 6 remote debugging protocol</a>. Use <code>chrome.debugger</code> | |
| 7 to attach to one or more tabs to instrument network interaction, debug | |
| 8 JavaScript, mutate the DOM and CSS, etc. Use the Debuggee tabId to target tabs | |
| 9 with sendCommand and route events by <code>tabId</code> from onEvent callbacks. | |
| 10 </p> | |
| 11 <p> | |
| 12 As of today, attaching to the tab by means of the debugger API | |
| 13 and using embedded Chrome DevTools with that tab are mutually exclusive. | |
| 14 If user invokes Chrome DevTools while extension is attached to the tab, | |
| 15 debugging session is terminated. Extension can re-establish it later. | |
| 16 </p> | |
| 17 <h2 id="manifest">Manifest</h2> | |
| 18 <p> | |
| 19 You must declare the "debugger" permission in your extension's manifest | |
| 20 to use this API. | |
| 21 </p> | |
| 22 <pre>{ | |
| 23 "name": "My extension", | |
| 24 ... | |
| 25 <b> "permissions": [ | |
| 26 "debugger", | |
| 27 ]</b>, | |
| 28 ... | |
| 29 }</pre> | |
| 30 <h2 id="examples">Examples</h2> | |
| 31 <p> | |
| 32 You can find samples of this API in | |
| 33 <a href="samples.html#debugger">Samples</a>. | |
| 34 </p> | |
| 35 <!-- END AUTHORED CONTENT --> | |
| OLD | NEW |