debugger protocol. protip on sniffing it. images for that. fixing bad links.

docs/debugger-protocol.html

@@ -65,6 +65,11 @@ builds at your own risk. Note that unless tip of the tree revision is promoted t
 draft, there is no backwards compatibility support guaranteed for the capabilities it
 introduces.</p>
 
+
+<p>DevTools may introduce new features that are not currently documented under the tip-of-tree protocol documentation. You can discover these if you want to try using features, however, the undocumented protocol is volatile and may break at any time. First, <a href="https://developers.google.com/chrome-developer-tools/docs/contributing#step_3_inspector_inception">inspect the inspector</a> and reload the inspector so your attached one can view its WebSocket connection (<code>Network > Filter > WebSockets</code>). Then view the frames of WebSocket activity as you use the host DevTools. You may need to re-click the WebSocket item to have the Frame activity update.</p>
+
+<figure class="screenshot"> <a href="debugger-protocol/debugger-protocol-sniffing-full.jpg"><img src="debugger-protocol/debugger-protocol-sniffing.jpg" alt="Sniffing the debugger protocol" /></a></figure>
+
 <h2 id="remote">Debugging over the wire</h2>
 <p>Today Developer Tools front-end can attach to a remotely running Chrome
 instance for debugging.

docs/protocol/0.1/index.html

@@ -15,9 +15,9 @@
 <p>Instrumentation is divided into a number of domains (DOM, Debugger, Network
 etc.). Each domain defines a number of commands it supports and events it
 generates. Both commands and events are serialized JSON objects of a fixed
-structure. You can either <a href="/chrome-developer-tools/docs/remote-debugging.html#remote">debug
+structure. You can either <a href="/chrome-developer-tools/docs/debugger-protocol#remote">debug
 over the wire</a> using the raw messages as they are described in the corresponding domain
-documentation, or use <a href="/chrome-developer-tools/docs/remote-debugging.html#extension">extension
+documentation, or use <a href="/chrome-developer-tools/docs/debugger-protocol#extension">extension
 JavaScript API.</a>
 </p>
 

docs/protocol/1.0/index.html

@@ -15,9 +15,9 @@
 <p>Instrumentation is divided into a number of domains (DOM, Debugger, Network
 etc.). Each domain defines a number of commands it supports and events it
 generates. Both commands and events are serialized JSON objects of a fixed
-structure. You can either <a href="/chrome-developer-tools/docs/remote-debugging.html#remote">debug
+structure. You can either <a href="/chrome-developer-tools/docs/debugger-protocol#remote">debug
 over the wire</a> using the raw messages as they are described in the corresponding domain
-documentation, or use <a href="/chrome-developer-tools/docs/remote-debugging.html#extension">extension
+documentation, or use <a href="/chrome-developer-tools/docs/debugger-protocol#extension">extension
 JavaScript API.</a>
 </p>
 

docs/protocol/1.1/index.html

@@ -15,9 +15,9 @@
 <p>Instrumentation is divided into a number of domains (DOM, Debugger, Network
 etc.). Each domain defines a number of commands it supports and events it
 generates. Both commands and events are serialized JSON objects of a fixed
-structure. You can either <a href="/chrome-developer-tools/docs/remote-debugging.html#remote">debug
+structure. You can either <a href="/chrome-developer-tools/docs/debugger-protocol#remote">debug
 over the wire</a> using the raw messages as they are described in the corresponding domain
-documentation, or use <a href="/chrome-developer-tools/docs/remote-debugging.html#extension">extension
+documentation, or use <a href="/chrome-developer-tools/docs/debugger-protocol#extension">extension
 JavaScript API.</a>
 </p>
 

docs/protocol/tot/index.html

@@ -15,9 +15,9 @@
 <p>Instrumentation is divided into a number of domains (DOM, Debugger, Network
 etc.). Each domain defines a number of commands it supports and events it
 generates. Both commands and events are serialized JSON objects of a fixed
-structure. You can either <a href="/chrome-developer-tools/docs/remote-debugging.html#remote">debug
+structure. You can either <a href="/chrome-developer-tools/docs/debugger-protocol#remote">debug
 over the wire</a> using the raw messages as they are described in the corresponding domain
-documentation, or use <a href="/chrome-developer-tools/docs/remote-debugging.html#extension">extension
+documentation, or use <a href="/chrome-developer-tools/docs/debugger-protocol#extension">extension
 JavaScript API.</a>
 </p>