search

MilesMcBain / chradle

A bare bones #rstats test harness for Chrome/Chromium
Other
7 stars 1 forks source link

Documentation for Chrome debugger API #1

Open MilesMcBain opened 6 years ago

MilesMcBain commented 6 years ago

Documentation on how to actually form the websocket messages to be read by the Chrome/chromium debugger is scant. After much searching I happened upon this stack overflow question: https://stackoverflow.com/questions/28430479/using-google-chrome-remote-debugging-protocol/28432503#28432503 which lead me to this blog post: https://www.igvita.com/2012/04/09/driving-google-chrome-via-websocket-api/

From my testing it seems as though the id field is currently not important, it is just reflected back by the debugger.

Once you understand the JSON structure expected by the API the documentation is actually quite good: https://chromedevtools.github.io/devtools-protocol/

RLesur commented 5 years ago

Thanks @MilesMcBain for your work! Here's another article I've found https://medium.com/@lagenar/using-headless-chrome-via-the-websockets-interface-5f498fb67e0f