console.debug method doesn't work as described in docs
Reported by
sfrie...@theatermania.com,
Nov 29 2017
|
||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36
Steps to reproduce the problem:
1. Open developer console
2. Run `console.debug({foo: 'bar'})`
What is the expected behavior?
As per the documentation linked below, I am expecting the same behavior as the console.log method, which would log my input.
https://developers.google.com/web/tools/chrome-devtools/console/console-reference#consoledebugobject_object
What went wrong?
I received `undefined`, which is consistent with console.log, but I did not receive the actual log.
Did this work before? N/A
Chrome version: 62.0.3202.94 Channel: stable
OS Version: OS X 10.12.6
Flash Version:
,
Nov 30 2017
1. The console filter selector hides debug messages by default. Click "Default levels" in the console toolbar and enable "Verbose". Apparently, according to chromium developers who introduced the change it's rarely used. 2. You've received "undefined" for the evaluated statement "console.debug()" itself, which doesn't have a return value, hence "undefined".
,
Nov 30 2017
As per comment #2.
,
Nov 30 2017
Thank you for the clarification in comment #2.1. Maybe this is the wrong platform for this request, but if this is the case, then it seems that the documentation page should be updated. console.debug() is not "Identical to console.log()" if they have different verbosity levels.
,
Nov 30 2017
This report no longer has any developers assigned (no CC or Owner in the header sidebar) so maybe you could notify the authors of the documentation, there's a link at the bottom of the page: https://github.com/google/WebFundamentals/issues |
||
►
Sign in to add a comment |
||
Comment 1 by manoranj...@chromium.org
, Nov 29 2017