Issue metadata
Sign in to add a comment
|
Filtering logs should hide console groups, not collapse them
Reported by
akl...@gmail.com,
Mar 28 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36 Steps to reproduce the problem: 1. Execute a console.group in the Console tab of the devtools 2. In the filter input type something that should not much the group's text What is the expected behavior? I was expecting the console group to be filtered out and hide What went wrong? Instead what I got was a collapsed console group Did this work before? No Chrome version: 57.0.2987.110 Channel: stable OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 25.0 r0 This is really not an issue if you execute a couple of console.groups but if you start doing anything serious like for example what Matt describes here -> https://medium.com/dev-channel/pretty-printing-d80639fb8881 it becomes a living hell trying to filter things out because the collapsed groups are everywhere taking precious space in your filtered out console tab.
,
Mar 31 2017
Unable to reproduce the issue on Mac 10.12.4 using stable 57.0.2987.110 and latest stable 57.0.2987.133, canary 59.0.3057.0. Could you please review the attached screen cast let us know if any steps are missed here.
,
Mar 31 2017
I don't think you understand what I'm talking about. The problem is not the code I've entered in the console.log input but the logged results. For example the "My Custom Heading 1" title remains even though the filter entered doesn't match the content of "My Custom Heading 1" group's content or title.
,
Mar 31 2017
Thank you for providing more feedback. Adding requester "durga.behera@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
,
Apr 6 2017
,
Apr 6 2017
Thank you for the report. I believe that what you described matches with a comment in another bug, "1. Groups should not remain if their group name doesnt match and there are no matching child logs" https://bugs.chromium.org/p/chromium/issues/detail?id=363796#c1
,
Apr 12 2017
@luoe you are correct to assume that this issue matches what was described in that issue's comment but that particular issue is made for another reason and by marking this as duplicate might lose the attention it deserves (IMHO).
,
Apr 12 2017
I see your concern. I agree that there's really 2 changes that should be made 1) showing group children that are incorrectly hidden 2) hiding groups entirely when they are incorrectly shown. To me, these are related enough that discussion around either one might benefit the other. Comments regarding one might bring up use cases that likely affect the other, so I'd rather have a single thread of communication. We can definitely adjust the title of the other bug, though, and repost your great GIF for reference. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by akl...@gmail.com
, Mar 28 2017