Issue metadata
Sign in to add a comment
|
The Logs console filter is not available anymore
Reported by
daniel.o...@gmail.com,
May 11 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.47 Safari/537.36 Steps to reproduce the problem: 1. Open developer tools 2. Click on the new console verbosity level selector next to the filter field 3. The Logs option in the selector is not there anymore and it was in previous versions of Chrome What is the expected behavior? See the Logs option in the console verbosity level selector and be able to filter the console by js log statements What went wrong? At least from Chrome 58.0.3029.110 that changed and that option disappeared. I attached a picture of how it looked before, with the Logs option present Did this work before? Yes Not sure, but I see that option disappearing in 58.0.3029.110 Chrome version: 59.0.3071.47 Channel: beta OS Version: OS X 10.12.3 Flash Version:
,
May 12 2017
This issue looks similar to the issue id: 717776. Hence, merging into it. Please feel free to undupe the same if not the case. Thanks...!! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by kavvaru@chromium.org
, May 11 2017