console.debug() seems to have stopped working correctly
Reported by
ad...@logicaloctopus.com,
May 3 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36 Steps to reproduce the problem: 1. use `console.debug(data)` in js code anywhere or type it directly into 'Console' in the inspector 2. observe that no output is produced What is the expected behavior? It used to dump out the data pretty much the same as console.log does now. What went wrong? No output. Did this work before? N/A Chrome version: 58.0.3029.81 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: I can use console.log to do exactly what I need currently, but since console.log used to work only with strings I used to use console.debug for objects and arrays. Now much of my older dev code (with debugging info) no longer works without updating it. Maybe console.debug has been deprecated but I can find no documentation on that. Other browsers (Firefox, IE) still seem to support it.
,
May 4 2017
The new devtools console UI is counter-intuitive, misleading and less functional: now the log level filter dropdown selector specifies the minimum level to display in the console. You need to switch it to Verbose to see console.debug messages.
,
May 4 2017
Unable to reproduce the issue on Win-7 and Win-10 using chrome reported version #58.0.3029.81 and latest canary #60.0.3088.3. Attached a screen cast for reference. Following are the steps followed to reproduce the issue. ------------ 1. Typed `console.debug(data)` in 'Console' in the inspector 2. Observed that output "console.debug(data)" was produced successfully. Reporter@ - Could you please check this issue on latest canary #60.0.3088.3 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Thanks...!!
,
May 4 2017
#3, krajshree@, you did not correctly reproduce the issue. Typing text in quotes is not the same as running it as a command. Paste and run console.debug('test')
,
May 4 2017
Woxxom said it right in comment#2. So why is the default level not 'Verbose'? It would save people from facing this same issue, but still allows them to filter some of the noise when they realize that feature is there.
,
May 4 2017
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 4 2017
,
Oct 4 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ligim...@chromium.org
, May 3 2017