Hosted DevTools too restrictive
Reported by
raina...@gmail.com,
May 3 2017
|
|||
Issue descriptionThe last few days I've REALLY dug into DevTools on Canary (60.0.3088.0 64-bit so I'd have the latest in Node.js debugging support) with node.js and it's wonderful! That said, I rely heavly on a Chrome Extension called NiM (https://chrome.google.com/webstore/detail/nodejs-v8-inspector-manag/gnhhdgbaldcilmgcpfddgdbkhjohddkj) which I'm hoping you all know and love as well. It makes the actual workflow of watching node for restarts, maintaining the devtools instance coordination with the currently running debugger. Without it, I'd have to use chrome://inspect to launch each time and close the window each time. I find it WAY too easy to lose track on top of the extra effort and though it doesn't sound like much, it really makes a big difference when I'm dug in debugger. All debugger features aren't available with the NiM workflow though because the devtools instance is hosted. Is this an issue you guys are already aware of and reviewing? Possible to remove those restrictions until the built-in node support makes the overall workflow easier (negating NiM), add a whitelist for NiM or otherwise coordinate with the developer so that we have full debugging support AND the workflow NiM provides? Chrome Version : 60.0.3080.5 OS Version: 10.0 URLs (if applicable) : DevTools/Node.js, no URLs Other browsers tested: n/a What steps will reproduce the problem? 1. Install NiM from https://chrome.google.com/webstore/detail/nodejs-v8-inspector-manag/gnhhdgbaldcilmgcpfddgdbkhjohddkj 2. `node --inspect index.js` any node app 3. Launch NiM using extension icon or set it to automatic mode (it will open its own tab) 4. Try one of the following: A) Add a variable to the watch list then try to use the context menu 'copy value' option. B) Try to use the console execution history (up/down arrows) C) Try to inspect an object in the console by executing `someObject` What is the expected result? I expect the devtools features to work. What happens instead of that? I see errors logged in the console stating "Clipboard is not enabled in hosted mode. Please inspect using chrome://inspect" Please provide any additional information below. Attach a screenshot if possible. UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3080.5 Safari/537.36
,
May 4 2017
,
May 13 2017
This is not a DevTools issue, it is genuine restrictions of the platform.
,
May 17 2017
Same issues here then right? https://chrome.google.com/webstore/detail/nodejs-v8-inspector/lfnddfpljnhbneopljflpombpnkfhggl That plugin is doing essentially the same things with the same APIs?
,
May 17 2017
Have a relevant update to anyone that might find themselves looking at this bug, but it's not really about the bug (which is closed at this point). I'm not convinced that I've just been overlooking this the entire time and it's possible that something has changed (if so, recently I think) because right now if I visit chrome://inspect and click on `Open dedicated DevTools for Node`, then I get what I have been wanting; a fully function debugger (no 'blank panel' bug in Profile @PaulIrish) that maintains its connection to my app as it restarts! In Version 60.0.3100.0 (Official Build) dev (64-bit), the console appears broken at the moment though so I'm still using Version 60.0.3102.0 (Official Build) canary (64-bit) for this approach. Hope this helps someone else. |
|||
►
Sign in to add a comment |
|||
Comment 1 by paulir...@chromium.org
, May 4 2017