Can't press enter to run commands in console when remotely debugging using CEF

Issue #2049 wontfix
ldlchina created an issue

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

Comments (2)

  1. ldlchina reporter

    Hi Marshall,

    Yes, The latest CEF has no the problem. Our product is using 3.1650.1562, it's stable for several years, it's not easy to update to the latest CEF in short term. Because our product is very complex, that may require a lot of changes to integrate to the latest CEF. And the product has thousands of customers, so we need to have abundant test to avoid regression.

    Do you know what are the changes in the latest CEF (based on Chromium 54.0.2840.99) or CEF test app (CEFClient) to resolve this problem? That will help us find a workaround in short term.

    Many thanks.

  2. Log in to comment