Re:Show HN: Chrome Remote Debugging Protocol interface
by pault on Monday August 29, 2016 @01:28PM
(#12383509)
What is the use case for this? Testing? Scraping?
[ Parent
| on HN ]
Re:Show HN: Chrome Remote Debugging Protocol interface
by paulirish on Monday August 29, 2016 @01:44PM
(#12383640)
Everything, really. The protocol is a layer underneath the WebDriver protocol, and what Chrome DevTools uses. So it's pretty much the most complete API for the browser; in fact, Chrome is shipping the protocol as the 1st class API for headless Chrome .
We use it in Lighthouse [0] to reload the browser, manipulate ServiceWorkers and caches, execute a bunch of tests on pages and measure performance characteristics. I've also used it for automated profiling [1], in case you want to profile your JS with a bit more control. Using this for testing or scraping would work as well, but you might as well move a layer up and use WebDriver as the commands will be fairly common.
[0] https://github.com/GoogleChrome/lighthouse/
[1] https://github.com/paulirish/automated-chrome-profiling/
Re:Show HN: Chrome Remote Debugging Protocol interface
by ianbicking on Monday August 29, 2016 @07:45PM
(#12386324)
How realistic do you think it is to add to the protocol? I've played with it some and it can be great for what it has, but I want just a little bit more... like a way to view user-generated events. I'm debating whether to play with an extension, or with the protocol itself.