New issue
Advanced search Search tips

Issue 704564 link

Starred by 1 user
Status: WontFix
Owner:
kozy@chromium.org
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

Headless Chrome: Console domain is deprecated but console messages not triggering Log.entryAdded

Reported by fastest...@gmail.com, Mar 23 2017 
Chrome Version       : Google Chrome 59.0.3047.0 dev
URLs (if applicable) : http://gobin.io/NaMy

The above url logs a message to the console using console.log.

What steps will reproduce the problem?
(1) Create a browser context and target
(2) Navigate that target to http://gobin.io/NaMy

What is the expected result?
I expect to see a Log.entryAdded.

What happens instead?
I only see Console.messageAdded.

Please provide any additional information below. Attach a screenshot if
possible.

Chrome logs:
[0323/152350.778214:INFO:CONSOLE(1)] "hello", source: http://gobin.io/NaMy (1)
Attached is a pcap of all traffic going over the devtools port.
console.pcap
24.8 KB Download

Comment 1 by fastest...@gmail.com, Mar 23 2017 

Additionally, I'm not seeing either domain report javascript errors that are logged to the console:
[0323/154520.101545:INFO:CONSOLE(1)] "Uncaught TypeError: window.unknownfunction is not a function", source: http://gobin.io/cGHo (1)

What about CSP errors? Can I expect those to be reported to Console/Log domains?

Comment 2 by ranjitkan@chromium.org, Mar 27 2017

Labels: Needs-Triage-M59

Comment 3 by sureshkumari@chromium.org, Mar 28 2017

Labels: TE-NeedsTriageHelp

Comment 4 by skyos...@chromium.org, Mar 30 2017

Components: Platform>DevTools
Status: Untriaged (was: Unconfirmed)
Console.messageAdded is probably fine for now, but I'm not sure about the long term plans. DevTools folks?

Comment 5 by allada@chromium.org, Apr 6 2017

Owner: kozyatinskiy@chromium.org

Comment 6 by skyos...@chromium.org, May 15 2017

Components: Internals>Headless

Comment 7 by kozyatinskiy@chromium.org, Oct 16 2017

Owner: kozy@chromium.org

Comment 8 by kozy@chromium.org, Oct 16 2017

Status: Assigned (was: Untriaged)

Comment 9 by kozy@chromium.org, Oct 18 2017

Status: WontFix (was: Assigned)
Console.messageAdded was spitted into three events:
- Runtime.exceptionThrown for uncaught exceptions,
- Runtime.consoleAPICalled for console.* calls from JavaScript,
- Log.entryAdded - for other Chromium messages, including CSP errors.
►

Sign in to add a comment