Devtools: Console contents remain despite "Preserve Log" setting being off, with AdBlock installed
Reported by
cde...@gmail.com,
Apr 24 2018
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36 Steps to reproduce the problem: 1. Open DevTools console 2. Open the console settings 3. Verify that "Preserve Log" is unchecked 4. Close settings 5. Generate some log statements through normal web site use 6. Refresh the page 7. Note that the previous console contents are still visible What is the expected behavior? Console contents should clear when the page is refreshed What went wrong? Console contents remained after the page was refreshed Did this work before? Yes 63 Chrome version: 66.0.3359.117 Channel: stable OS Version: OS X 10.11.6 Flash Version:
,
Apr 25 2018
Unable to reproduce the issue reported version on 66.0.3359.117 by using Mac 10.12.6. Attaching Screencast for reference. Steps -------- 1. Opened DevTools console 2. Navigated to console settings 3. Observed that ""Preserve Log"" is unchecked by default 4. Observed the issue by Unchecking & Checking the ""Preserve Log"" 5. Generated some log statements through normal web site and refreshed page 6. Previous console contents are not visible for me. As we are unable to reproduce the issue from our end. Can you verify this issue with fresh profile that is not having any extensions and apps.Let us know still issue is persists. Thanks!
,
Apr 27 2018
Thanks for the report. I'm also unable to reproduce this, but since OP says it used to work in 63, I'm guessing it might be related to out-of-process-iframes (OOPIFs). - Does this bug reproduce in Chrome Canary? It might contain OOPIF fixes for this case. - Do you happen to have a link that you can share publicly for us to reproduce? - Could you please check the DevTools-on-DevTools Console and see if there are errors? [1] [1] https://stackoverflow.com/questions/12291138/how-do-you-inspect-the-web-inspector-in-chrome/12291163#12291163
,
Apr 27 2018
Looks like it works properly in Canary! Unfortunately I don't have a public link I can share, but after investigating a bit further it looks like it only happens for Webpack dev-server sites. Your guess regarding OOPIFs seems spot-on. Obviously it's been fixed in the Canary release, but if it helps I've attached the errors I get from the DevTools-on-DevTools console.
,
Apr 30 2018
I'm not sure your repro video is correct - I have attached a video also showing this behaviour, as well as a screenshot of the devtools-on-devtools console, there are error. Hope this helps.
,
Apr 30 2018
It appears that you are using the AdBlock Plus extension. I am using that as well and believe it may be the culprit. Can you disable the extension and retry the test? This works in my case.
,
Apr 30 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 1 2018
I can confirm that disabling Adblock Plus fixes this issue.
,
May 2 2018
Able to reproduce the issue by adding adblocker extension on reported version 66.0.3359.117 and latest chrome 68.0.3416.0 on Mac 10.12.6,Windows 10 and linux 14.04. Similar behavior is seen on older chrome version m-60(60.0.3112.113) as well. As per comment#7 and comment#9 the issue seems to be resolved after disabling the AdBlock Plus extension. However, since this repros only with adblock plus added hence marking this as Untriaged and for more inputs on this. Thanks!
,
May 2 2018
,
May 2 2018
phanindra.mandapaka@chromium.org Please refer to my comments comment#3 and comment#5. The issue is reproducible without AdBlock. In my case, it happens when running a Webpack dev-server. However, for me, it works now in Canary. Because of that, I think there might be two slightly different issues that are appearing here.
,
May 2 2018
Glad to hear the original reporter's bug was fixed! If that was the only case, we'd close this crbug, but since there is a separate bug with the exact same repro steps (+ adblock plus), I'll update the report description. Comments #5, #6, thanks a ton for the screenshots. #10, can you please send me the public site you used to reproduce this? I installed the extension but still cannot reproduce the issue.
,
May 2 2018
,
May 29 2018
Without being able to reproduce this w/ AdblockPlus on 66.0.3359.181 or 68.0.3440.0, I'm marking as WontFix. If others have more info or a test case to help us investigate, please add a comment and we'll take another look. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by krajshree@chromium.org
, Apr 25 2018