@@ -34,9 +34,10 @@ The stable release of the protocol, tagged at Chrome 64. It includes a smaller s
3434
3535<p >Consider subscribing to the <a href =" https://groups.google.com/d/forum/chrome-debugging-protocol " >chrome-debugging-protocol</a > mailing list.
3636
37- <h3 id =" monitor " >Monitoring the protocol</h3 >
37+ <h3 id =" monitor " >Inspect the protocol using Protocol Monitor in DevTools </h3 >
3838<p >This is especially handy to understand how the DevTools frontend makes use of the protocol.
39- You can view all requests/responses and methods as they happen.
39+ You can view all requests/responses and methods as they happen in the Protocol Monitor
40+ panel in DevTools.
4041
4142<figure class =" screenshot " >
4243 <a href =" images/protocol-monitor.png " target =" _blank " style =" text-align : center ; display :block ;" >
@@ -48,7 +49,7 @@ Click the gear icon in the top-right of the DevTools to open the <i>Settings</i>
4849Select <i >Experiments</i > on the left of settings. Turn on "Protocol Monitor", then close and reopen DevTools.
4950Now click the ⋮ menu icon, choose <i >More Tools</i > and then select <i >Protocol monitor</i >.
5051
51- <p >You can also issue your own commands using Protocol Monitor. If the command does not require any parameters,
52+ <p >You can also send commands using Protocol Monitor. If the command does not require any parameters,
5253type the command into the prompt at the bottom of the Protocol Monitor panel and press Enter, for example,
5354<code >Page.captureScreenshot</code >. If the command requires parameters, provide them as JSON, for example,
5455<code >{"cmd":"Page.captureScreenshot","args":{"format": "jpeg"}}</code >.
0 commit comments