Page reload does not clear console filter
Reported by
ryan.bur...@definitiv.com.au,
Oct 9
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Open Dev Tools 2. Go to console 3. Go to a page that logs an error 4. Add a filter at the top that does not match the error so it is excluded from the console results. 5. Trigger the error. Nothing is displayed as expected 6. Reload the page 7. Trigger the error. The error is still not displayed due to the filter being persisted. What is the expected behavior? The default behaviour should be to clear any filter of the console on page reload. What went wrong? Wasted an hour or two trying to figure out why errors were being swallowed. I thought it was a promise that was not handling errors but turned out i had accidentally pasted some junk into the Console filter which meant it was not showing in the console. Combine this with it not being very obvious that a filter is applied meant a lot of wasted time. If it cleared on page reload then it would have corrected itself as soon as i made a code change. Did this work before? N/A Chrome version: 69.0.3497.100 Channel: stable OS Version: 10.0 Flash Version:
,
Oct 9
that's why i mentioned the Default should be. I think highlight would be a good addition but i think it should also work similar to the 'Preserve Log' option that preserves the entries between reloads. Perhaps a 'Preserve Filter' checkbox next to the input field.
,
Oct 9
,
Oct 9
We have "<x> hidden" text at the top-right of Console, which shows how many messages were filtered out. I don't think we need any additional visual clues. Does that hint work for you?
,
Oct 10
Well i didn't notice that until about 2 hours in. It's easy to look over.
,
Oct 10
Able to reproduce the issue on chrome version #60.0.3072.0, reported chrome version #69.0.3497.100 and latest canary 71.0.3575.0 on windows 10, Mac10.12.6 and Ubuntu 17.10 by following steps as per comment#0. Note: "https://www.walmart.com/" is used for reproducing the issue. This is non-regression issue and the behavior is seen from old M-60 builds, hence marking is as untriaged and requesting someone from the dev team to kindly look into the issue. Thanks.!
,
Oct 15
,
Dec 5
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by woxxom@gmail.com
, Oct 9