Issue metadata
Sign in to add a comment
|
console.group seems broken
Reported by
holmes.w...@gmail.com,
Aug 1 2017
|
||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.78 Safari/537.36
Steps to reproduce the problem:
1. Open console tab
2. type let test = () => { console.group('Title'); console.log(134); console.groupEnd();}
3. type test();
4. press enter
What is the expected behavior?
The console group should have the 'Title' which when expended should include the console.log passed value (134).
What went wrong?
The console group did NOT include the console log when expanded
Did this work before? Yes 59.0.3071.115
Chrome version: 60.0.3112.78 Channel: stable
OS Version: OS X 10.12.5
Flash Version:
,
Aug 1 2017
The observed behavior is intended, even though it's confusing. Luckily, UX was salvaged in Chrome 61: the ability to select individual types was re-introduced. Which info is shown depends on the type selector in the console toolbar. In your case Chrome 60 was set to something like "Errors" or "Warnings" and thus all lower levels like "Info" or "Debug" were excluded.
,
Aug 1 2017
Actually after installing Chrome 60, it was set to "Hide All", however i'm not 100% sure if this was manually set (by mistake) previous to the update.
,
Aug 1 2017
,
Aug 1 2017
Thanks for the report. It looks like this was working as intended, but the "Hide all" UX could be improved. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by holmes.w...@gmail.com
, Aug 1 2017