Can you provide more information on how to reproduce this? What's your remote target? If you can include a movie / animated gif, that would help us understand your issue.

Dear chenwilliam,

My remote target was our webos device, but any chromium based engine can be a remote target with having the command line option like --remote-debugging-port=9222.
Also I debug this issue and found an issue regarding devtools_frontend_url path. I uploaded a patch for this https://codereview.chromium.org/2575363002/ and I am waiting the review.

Thanks.

To reproduce this issue. (simple way)
1) launch chrome like below.
 chrome --remote-debugging-port=9222
2) visit google.com
3) open one more tab
4) visit chrome:inspect
5) check Discover network targets and click Configure next to it.
6) add localhost:9222 then click done
7) click inspect link below google.com in Remote Target
: Inspector is not working

Thanks

I tried reproducing 57.0.2953.0 (Developer Build) (64-bit) on Linux but it seems to be working as expected for me. Can you provide a screencast / video recording? It would help clarify how inspector is not working for you.

I made screen record with the latest chromium version which I synced today and built.
Please chech the video clip I uploaded.

Deleted: remote-target-inspector.mp4 1.3 MB

	remote-target-inspector.mp4 1.3 MB View Download

It does work fine for me as well. However, I don't think it is implemented quite right - it would not work if the remote target is of a different version. We should use remote front-end link when inspecting remote targets.

Could you take a look more information on the https://codereview.chromium.org/2575363002/. I summary what I debug.

Thanks.

Had been fixed some time ago.