New issue
Advanced search Search tips

Issue 714261 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Console log level not functioning

Reported by fgomez...@gmail.com, Apr 21 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36

Steps to reproduce the problem:
1. Open the console.
2. Cause an error to be reported on console.
3. Set log level to "info"
4. See the error logged in an info-level console.

What is the expected behavior?
Only messages of type info should be logged to the console.

What went wrong?
Errors and warning are shown on the console.

Did this work before? Yes Don't know version but it was working yesterday. I updated yesterday through the chrome://help page

Chrome version: 58.0.3029.81  Channel: stable
OS Version: OS X 10.11.6
Flash Version: 

Don't know version but it was working yesterday. I updated yesterday through the chrome://help page
 
Screen Shot 2017-04-21 at 14.47.56.png
316 KB View Download

Comment 1 by woxxom@gmail.com, Apr 21 2017

The new level selector means minimum level displayed, it's not a checkbox. And yes I agree, this is obviously worse than the old functionality. Unfortunately, the devtools team thinks otherwise.

Comment 2 by woxxom@gmail.com, Apr 21 2017

BTW, in Firefox the dropdown selector contains individually selectable levels for various types of console messages. Could it be that none of the chromium's devtools programmers who are responsible for this change ever used Firefox? I dislike Firefox generally, but in this case their solution seems obviously better.

Comment 3 by fgomez...@gmail.com, Apr 21 2017

I wasn't aware that it's a minimum level. I have an app that logs 15 errors per second when running in beta (because it's a sandbox, I don't need these calls. That doesn't happen on prod of course).

Comment 4 by caseq@chromium.org, Apr 23 2017

Cc: caseq@chromium.org
Status: WontFix (was: Unconfirmed)
The described behavior is by design. If your app is logging many log messages, consider a lower level for these (e.g. use console.log() instead of console.error()). You can also use filters in the console toolbar to filter only relevant messages.

Sign in to add a comment