Issue metadata
Sign in to add a comment
|
Can't press enter to run commands in console when remotely debugging using CEF
Reported by
ldlch...@gmail.com,
Nov 14 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36 Steps to reproduce the problem: 1. Download the test app (cefclient) of CEF 3.1650.1562 (64-bit). 2. Install Chrome 54.0.2840.99 m (64-bit) on Windows. 3. Enter "cefclient.exe --remote-debugging-p ort=12345" in Windows command console. 4. Open "http://localhost:12345/" or "http://127.0.0.1:12345/" in Chrome. 5. Input "1+2" in Chrome devtools console, press "Enter", nothing happened What is the expected behavior? Expect "3" is print in console. What went wrong? Can't press enter to run commands in console when remotely debugging using CEF Did this work before? Yes Chrome 53.0.2785.89 Chrome version: 54.0.2840.99 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 23.0 r0 It's a regression bug of Chrome 54.0.2840.99. The same workflow works with Chrome 53.0.2785.89.
,
Nov 14 2016
,
Nov 14 2016
This is due to feature deprecation in new Chrome version (KeyboardEvent.keyIdentifier this time). The workaround is to replace https://chrome-devtools-frontend.appspot.com/ with chrome-devtools://devtools/remote/ in address bar.
,
Nov 15 2016
Thanks you all for looking into this. How to fix this instead of workaround? I understand the change in Chrome may be reasonable. But it would be appreciated if you consider backward compatibility. Sometimes, it is expensive to provide a fix to big products which are using Chrome devtools to debug JS remotely.
,
Nov 15 2016
@dgozman, the url in address bar is http://localhost:12345/devtools/devtools.html?ws=localhost:12345/devtools/page/963c13e612e327410d737b8584f09c71, how to replace it with your work around you mentioned above?
,
Nov 15 2016
re #c4: we have backwards compatibility script, which works for chrome-devtools://devtools urls. Thus the workaround. @lushnikov: would custom devtools url help in this case?
,
Nov 16 2016
The original URL is http://localhost:12345/devtools/devtools.html?ws=localhost:12345/devtools/page/963c13e612e327410d737b8584f09c71, I changed it to chrome-devtools://devtools/devtools.html?ws=localhost:12345/devtools/page/963c13e612e327410d737b8584f09c71. It did not work. @dgozman, or anyone else, Could you have a try with the steps to reproduce the problem and try if the workaround works? Download the test app of CEF 3.1650.1562 (64-bit) from https://cefbuilds.com. Or reopen this regression bug for more investigation? Thanks
,
Nov 18 2016
re #c1: Link the issue in CEF: https://bitbucket.org/chromiumembedded/cef/issues/2049/cant-press-enter-to-run-commands-in. Though I think it is a Chrome bug, but not a CEF bug.
,
Nov 18 2016
#7: So i tried a few workarounds for your situation. The best which worked for me is actually use another instance of cefclient to debug the first one. So instead of starting chrome 54, starting cefclient and entering http://localhost:12345 in its navigation bar worked just fine. Unfortunately, that's the best I can suggest. Sorry for the inconvenience! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by l...@chromium.org
, Nov 14 2016