Issue metadata
Sign in to add a comment
|
Headless Chrome: Target.GetTargets doesn't exist
Reported by
ja...@getadmiral.com,
Feb 28 2017
|
||||||||||||||||||||
Issue description
Chrome Version : 58.0.3018.3
What steps will reproduce the problem?
(1) Call Target.GetTargets via /devtools/browser
What is the expected result?
I expect a list of targets.
What happens instead?
{"error":{"code":-32601,"message":"'Target.getTargets' wasn't found"},"id":1}
,
Feb 28 2017
It's not clear to me from the viewer site https://chromedevtools.github.io/debugger-protocol-viewer/tot/Target/ what calls should be made to what endpoints, so that definitely might be my fault here. I assumed that all Target.* calls should be sent to the browser endpoint. What endpoint should I be using instead of that one?
,
Feb 28 2017
I was starting with it, but I need to talk telemetry into working to land... https://codereview.chromium.org/2514933003/ a workaround is using Target.GetTargets on the first available target.
,
May 15 2017
,
May 26 2017
This also happens with { method: "Target.sendMessageToTarget" } from the /devtools/browser target
,
Oct 4 2017
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by eseckler@chromium.org
, Feb 28 2017