UserAgent: 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.
It is like a Chrome bug, but the Chromium guys asked me log a defect to cef. Link the issue in Chromium org: https://bugs.chromium.org/p/chromium/issues/detail?id=664919