|
|
|
|
|
by fake-name
3225 days ago
|
|
Get them to actually version their protocol first, maybe? As someone with a bunch of tooling around the dev-tools API, it's a huge pain in the ass to not be able to tell what functions the remote browser supports. There's a version number in the protocol description, but it's literally never been incremented as far as I've seen. https://github.com/ChromeDevTools/devtools-protocol/issues/6 |
|
It should be possible to get the running chrome version and to do feature detection over this protocol.
If it isn't, it's a bug