[DevTools] "Remote target connected" is misleading
Reported by
kaycebas...@gmail.com,
Feb 6 2017
|
|
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3003.0 Safari/537.36 Steps to reproduce the problem: My teammate was just trying to remote debug an Android device. He thought he was all set, because the Remote Devices panel said "Remote target" connected. I was only able to spot it b/c I've heard other people get confused by this. What is the expected behavior? What went wrong? I believe that the "remote target" thing refers to some of the new support for Node.js debugging. I suggest renaming this to something else so that our users don't have frustrating "false positive" experiences like this anymore. Did this work before? No Chrome version: 58.0.3003.0 Channel: canary OS Version: OS X 10.12.3 Flash Version:
,
Feb 24 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2b7d72f872ab3c2e590ac008c7dd8ac426982d48 commit 2b7d72f872ab3c2e590ac008c7dd8ac426982d48 Author: dgozman <dgozman@chromium.org> Date: Fri Feb 24 22:48:49 2017 [DevTools] Fix 'node targets available' not appearing, but listed in Remote Devices drawer tab. Instead, those should be in ThreadsSidebarPane, but not in Remote Devices tab. BUG= 689131 Review-Url: https://codereview.chromium.org/2715783002 Cr-Commit-Position: refs/heads/master@{#452969} [modify] https://crrev.com/2b7d72f872ab3c2e590ac008c7dd8ac426982d48/third_party/WebKit/Source/devtools/front_end/devices/DevicesView.js [modify] https://crrev.com/2b7d72f872ab3c2e590ac008c7dd8ac426982d48/third_party/WebKit/Source/devtools/front_end/sources/ThreadsSidebarPane.js |
|
►
Sign in to add a comment |
|
Comment 1 by kozyatinskiy@chromium.org
, Feb 6 2017Status: Assigned (was: Unconfirmed)