New issue
Advanced search Search tips

Issue 695861 link

Starred by 1 user
Status: WontFix
Owner:
pfeldman@chromium.org
Closed: Feb 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

console.debug doesn't log

Reported by eldo...@gmail.com, Feb 24 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. open DevTools
2. write console.debug("test") in console
3. run the command

What is the expected behavior?
The string "test" is printed in console

What went wrong?
The function just return undefined and nothing is printed

Did this work before? Yes I think it was working on 58.0.3020.1

Chrome version: 58.0.3022.0  Channel: canary
OS Version: 10.0
Flash Version: Shockwave Flash 25.0 r0

Comment 1 by woxxom@gmail.com, Feb 24 2017 

It's printed, actually.
Change the filter on the top of the console tab to "Verbose".

Comment 2 by eldo...@gmail.com, Feb 24 2017 

Oops! You're right, I'm really sorry.

Is it something changed with the filters anyway? Because I don't think I ever changed that and I'm sure I was seeing "debug" logs too before...

Comment 3 by woxxom@gmail.com, Feb 24 2017 

The UI is being overhauled currently and apparently the developers decided on "Info" as the new default level of console verbosity. Seems reasonable because I think 99% of console messages are printed with console.log so the change won't affect real world use cases.

Comment 4 by eldo...@gmail.com, Feb 24 2017 

Thanks for the clarification, this "non-bug" can be closed.

Comment 5 by lushnikov@chromium.org, Feb 24 2017

Owner: pfeldman@chromium.org
Status: WontFix (was: Unconfirmed)
►

Sign in to add a comment