1<!-- BEGIN AUTHORED CONTENT --> 2 3 4<h2>Notes</h2> 5 6<p> 7Debugger API exposes Google Chrome debugging interface to the extensions. 8Debugging messages that are being sent and received are all JSON objects 9with the structure defined by the Developer Tools / Web Inspector Protocol. 10We are currently drafting this protocol, it is by no means ready and stable, 11but we can already expose the way to attach to a given tab and instrument it. 12Although not finalized, this API is feature rich. There is a proof of concept 13implementation of the Chrome Developer Tools front-end running as an extension 14using the debugger API. 15</p> 16 17<p> 18Note that attaching to the page by means of the debugger API and using embedded 19Chrome Developer Tools with it are mutually exclusive. If extension is attached 20to the page and user invokes Developer Tools, debugging session is being 21terminated. Extension can then re-establish it via attaching to a tab later. 22</p> 23 24<!-- END AUTHORED CONTENT --> 25