Mathias Fredriksson

With 10k users it would definitely be very resource intensive to use `devtool.New` and `rpcc.Dial` for each request. If you're looking to use only one Chrome instance with many connections,...

Hi @zfLQ2qx2, the protocol does allow you to do most of these things but it is quite low-level and some functionality can only be achieved by evaluating JavaScript on the...

It's not necessary to use `/json/list` if you know the address/port and the target ID. The websocket URL can be constructed: `fmt.Sprintf("ws://%s:%s/devtools/page/%s", browserIP, port, targetID)`. It's also possible to utilize...

@crislin2046 this project is focused on using the DevTools protocol in Go. Your comment does not answer the question presented here and this is not a forum for advertising your...

I see what you mean, I hadn't considered closing a target before the `rpcc.Conn`. I think we can detect this and close the conn without error. This means that `rpcc.ErrConnClosing`...

Hi, they were pulled from the JSON in [ChromeDevTools/devtools-protocol](https://github.com/ChromeDevTools/devtools-protocol) on Jul 10, so that should be `r674637`. But on that note, unless you're using bleeding edge methods, there shouldn't be...

PS. For best compatibility, pulling the protocol from the running browser (`http://localhost:9222/json/protocol`) and generating the cdp protocol from that would be the best option. Unfortunately, at the time of writing,...

> The problem I'm facing is that the protocol works weird with new versions of Chrome. Not always, but its work is not consistently good or bad. Completely random issues...

Thanks for raising this issue, I'll need to give it some thought as to how this could be accomplished but it's a good feature request. In the first design of...

Right now it would be possible to execute each command in a goroutine, but order isn't fully guaranteed, and this looks like a use-case where that guarantee is needed. This...