chrome: Add support for devtools:// schema

[tomaszkunicki]

Describe the bug
In versions prior to CEF 125 we could use devtools:// url for nodejs debugging but it doesn't work anymore.

To Reproduce
Steps to reproduce the behavior:

1. Open node --inspect
2. You will see inspector port (i.e. 127.0.0.1:9229)
3. Open http://127.0.0.1:9229/json/list in browser to get url for the debugger
4. Copy "devtoolsFrontendUrl" property value
5. Open cefclient.exe and copy given url
6. In cefclient page can't be opened
7. It works in chrome though

Expected behavior
Debugger should open

Versions (please complete the following information):

• OS: Windows 11
• CEF 128 (last worked in CEF 124)

Additional context
Yes. Cefclient.exe not opening given url but chrome does it.

[magreenblatt]

Launch chrome://inspect in a chrome browser and connect that way. See issue #3740.

[tomaszkunicki]

@magreenblatt, thank you for your suggestion, but launching chrome://inspect in a Chrome browser doesn't address our issue. Using Chrome instead of CEF defeats the purpose of our implementation. Our goal is to open multiple debugger windows for multiple Node.js processes and manage them within our custom debugging application built on CEF. The inability to open the Node debugger in CEF since version 126 represents a degradation of CEF's features and negatively impacts its usability for our use case.

[magreenblatt]

Thanks for the explanation of your use case. I'll reopen this issue as an enhancement request.