Console/Log are missing from 1.2 about devtools-protocol HOT 5 CLOSED

There is a Runtime.consoleAPICalled that will let you receive console.log calls from the browser. You'll get the event after calling Runtime.enable.

from devtools-protocol.

Bumped into this last night. The Log.entry event does not handle console.log's in the browser. May have to use something in the Runtime domain.

from devtools-protocol.

So is Runtime.consoleAPICalled just a temporary workaround for this issue, or is Log.entry still the way to go in the future?

from devtools-protocol.

Thanks @pthieu and @samir-mahendra for digging into this. Looks correct.

Looks like for completeness one may want to listen to a number of different events:

• Log.entryAdded - Logs coming from within the browser
• Runtime.consoleAPICalled - A method from the public window.console API was called, including console.log
• Runtime.exceptionThrown - All javascript exceptions/errors. Note: Runtime.exceptionRevoked called if a promise rejection was unhandled but now, asynchronously was handled.
• A few more things around network activity: pending/complete XHRs, blocked requests, bad mime type, set-cookie errors... These are manually issued clientside (and not explicitly over the protocol).

FWIW you can see these listeners being setup in devtools' consoleModel.js.

from devtools-protocol.

This will be fixed by https://chromium-review.googlesource.com/c/chromium/src/+/744729

from devtools-protocol.