Issue metadata
Sign in to add a comment
|
Console log level not functioning
Reported by
fgomez...@gmail.com,
Apr 21 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: 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
,
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.
,
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).
,
Apr 23 2017
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 |
|||||||||||||||||||||||
Comment 1 by woxxom@gmail.com
, Apr 21 2017