Under the hood, Chrome Developer Tools is a web application written in HTML, JavaScript and CSS. It has a special binding available at JavaScript runtime that allows interacting with chrome pages and instrumenting them. Interaction protocol consists of commands that are sent to the page and events that -the page is generating. Although Chrome Developer Tools is the only client of -this protocol, there are ways for third parties to bypass it and start +the page is generating. Although Chrome Developer Tools is the primary client of +this protocol, including for remote debugging, there are ways for third parties to use it and start instrumenting browser pages explicitly. We will describe the ways it could be done below.
-Note: If you are interested in inspecting remote pages on Chrome for Android, please see the remote debugging documentation. For users wishing to implement custom inspection code using our debugger protocol instead, please use the guide below.
and getting a JSON object with information about inspectable pages along with the WebSocket addresses that you could use in order to start instrumenting them.
-Note that we are currently working on exposing an HTTP-based -protocol that does not require client WebSocket implementation.
Remote debugging is especially useful when debugging remote instances of the browser or attaching to the embedded devices. Blink port @@ -114,7 +108,7 @@ users.
Many applications and libraries already use the protocol. Some to collect performance data, others to breakpoint debug from another editor. There are libraries to access the raw protocol from Node.js and Python.
@@ -148,10 +142,29 @@ pages with the target application, set breakpoints there, evaluate expressions in console, live edit JavaScript and CSS, display live DOM, network interaction and any other aspect that Developer Tools is instrumenting today. -Note: opening embedded Developer Tools will terminate the -remote connection / detach the extension and will replace active debugger with -itself. We are working on allowing several clients to instrument the page -simultaneously.
+Opening embedded Developer Tools will terminate the +remote connection and thus detach the extension.
+ + + ++Upon disconnnection, a reason is provided to the outgoing client. (original patch). +
+ ++The third-party crmux project multiplexes incoming connections into single websocket connection and transparently matches and translates JSON-RPC request and response message IDs from single local range to multiple remote ranges of ID'. Events are dispatched to all clients.
+ + + +