Issue metadata
Sign in to add a comment
|
Can't press enter to run commands in consoles when remotely debugging or using node-inspector
Reported by
alaudic...@compcc.com,
Nov 2 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.34 Safari/537.36 Steps to reproduce the problem: 1. Start node-inspector 2. Connect 3. Try to run a command in the console by typing it and pressing enter What is the expected behavior? The command runs What went wrong? The command doesn't run and I get a carriage return. This only happens when remotely debugging or using node-inspector. When I debug locally, it works fine. Did this work before? Yes 53 Chrome version: 54.0.2840.34 Channel: beta OS Version: Flash Version: Shockwave Flash 23.0 r0
,
Nov 2 2016
I have the same issue with Chrome version 54 when remote debugging an embedded device. On Chrome 53 it worked just fine. The only workaround I have is to download this Chromium 53-based version: https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac/403392/ To add a little detail, the issue is not that Enter does not work, the problem is that pressing Enter does not execute the command. Pressing Enter does add a line break to the command typed into the debugger, just as what you'd sometimes get if you press Shift + Enter.
,
Nov 2 2016
,
Nov 2 2016
Similar to other reports, when trying to attach to a chromium-embedded-framework (CEF) process, I see the same behavior. Installed Chrome 51 and it works as expected. Apparently I didn't have to go that far back.
,
Nov 2 2016
Oh - I should say this is happening to me on Mac.
,
Nov 3 2016
Is this using node-inspector or Node native inspector protocol support (e.g. --inspect command line switch)?
,
Nov 3 2016
I get it when using node inspector or remote debugging.
,
Nov 3 2016
How do you start the node for debug - are you using "node --inspect" or the node-inspector module? Can you confirm this issue persists when you run the node with --inspect?
,
Nov 3 2016
,
Nov 3 2016
--debug-brk + node-inspector. The version of node I'm using (5.10.1) doesn't seem to support --inspect.
,
Nov 3 2016
Please file the issue against node-inspector (https://github.com/node-inspector/node-inspector). That project is not a part of the Chrome.
,
Nov 12 2016
I also met the same issue with Chrome 54. I'm using CEF. It worked with Chrome 48. I did not test with other Chrome Versions. Is it a regression bug of Chrome? Why need to file issue to node-inspector ot CEF?
,
Nov 13 2016
@eostroukhov@chromium.org, Can you tell why Chrome 53 works but not Chrome 54 with the same machine, same windows os, and same environment?
,
Nov 13 2016
Link a question from stackoverflow: http://stackoverflow.com/questions/40562563/chrome-inspector-console-does-not-work-with-version-54-0-2840-99
,
Nov 14 2016
I am also experiencing the same issue when using CEF. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ameenudd...@booking.com
, Nov 2 2016