Issue metadata
Sign in to add a comment
|
Javascript clearing after mistakenly detecting page navigation
Reported by
daalexbo...@gmail.com,
Feb 7 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Steps to reproduce the problem: 1. send a GET request to https://accounts.google.com/o/oauth2/iframe What is the expected behavior? The javascript console will clear , as the returned html from the above URL makes it think it is navigating away from the current page What went wrong? Persisting logs across webpages will show that the console believes it is navigating away from the current page, resulting in the console being wrongfully cleared. Did this work before? Yes Chrome version: 64.0.3282.140 Channel: stable OS Version: OS X 10.13.2 Flash Version: Sorry that I couldnt provide any other information, as I found this in the company that I work, and dont want to divulge too much private information.
,
Feb 7 2018
,
Feb 7 2018
Issue 809965 has been merged into this issue.
,
Feb 8 2018
Thanks for filing the issue! Checked the issue on reported chrome version 64.0.3282.140 and on the latest canary 66.0.3342.0 using Mac 10.13.1 with the steps mentioned below. 1. Launched Chrome 2. Navigated to the URL given in Comment#0 3. Inspect->Network tab->Reloading the page->Clicked on the link->Headers We are able to see the result similar to that of the attachment in C#0. Note: Attaching the screenshot from M60(60.0.3072.0), where similar result is seen. @Reporter: Could you please have a look at the screenshot provided with this comment and let us know if the issue is there, your confirmation helps us to triage the issue in a better way.
,
Feb 8 2018
I probably could have made this clearer... The issue is not what's in the response, but instead stems from performing this request from inside another web-page. A script on my webpage is performing a request to this URL in order to get data to use in the current page, but the JavaScript console treats it as page navigation and clears the console.
,
Feb 8 2018
Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 8 2018
,
Feb 8 2018
Issue 809947 has been merged into this issue.
,
Feb 8 2018
This is due to out-of-process iframe, regressed from M64. We should merge the fix to M65.
,
Feb 8 2018
,
Feb 9 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/4e44555895b1c2fb682e33ffdaf9860dbe33ea45 commit 4e44555895b1c2fb682e33ffdaf9860dbe33ea45 Author: Dmitry Gozman <dgozman@chromium.org> Date: Fri Feb 09 22:44:18 2018 [DevTools] Fix console problems with oopif - Do not clear console on iframe navigation; - Do not print "Navigated to ..." message on iframe navigation; - Do not reset all UIMessages on iframe navigation. Bug: 809970 Change-Id: I591872eae4d4276a9362180a53d7a6dce2dd56d5 Reviewed-on: https://chromium-review.googlesource.com/909864 Commit-Queue: Dmitry Gozman <dgozman@chromium.org> Reviewed-by: Pavel Feldman <pfeldman@chromium.org> Cr-Commit-Position: refs/heads/master@{#535860} [add] https://crrev.com/4e44555895b1c2fb682e33ffdaf9860dbe33ea45/third_party/WebKit/LayoutTests/http/tests/devtools/oopif/oopif-console-preserves-log-on-frame-navigation-expected.txt [add] https://crrev.com/4e44555895b1c2fb682e33ffdaf9860dbe33ea45/third_party/WebKit/LayoutTests/http/tests/devtools/oopif/oopif-console-preserves-log-on-frame-navigation.js [add] https://crrev.com/4e44555895b1c2fb682e33ffdaf9860dbe33ea45/third_party/WebKit/LayoutTests/http/tests/devtools/oopif/oopif-presentation-console-messages-expected.txt [add] https://crrev.com/4e44555895b1c2fb682e33ffdaf9860dbe33ea45/third_party/WebKit/LayoutTests/http/tests/devtools/oopif/oopif-presentation-console-messages.js [add] https://crrev.com/4e44555895b1c2fb682e33ffdaf9860dbe33ea45/third_party/WebKit/LayoutTests/http/tests/devtools/oopif/resources/empty.html [add] https://crrev.com/4e44555895b1c2fb682e33ffdaf9860dbe33ea45/third_party/WebKit/LayoutTests/http/tests/devtools/oopif/resources/error.html [modify] https://crrev.com/4e44555895b1c2fb682e33ffdaf9860dbe33ea45/third_party/WebKit/Source/devtools/front_end/bindings/PresentationConsoleMessageHelper.js [modify] https://crrev.com/4e44555895b1c2fb682e33ffdaf9860dbe33ea45/third_party/WebKit/Source/devtools/front_end/console_model/ConsoleModel.js [modify] https://crrev.com/4e44555895b1c2fb682e33ffdaf9860dbe33ea45/third_party/WebKit/Source/devtools/front_end/main/Main.js
,
Feb 9 2018
Actually, there is no need to merge this to 65.
,
Feb 9 2018
[Auto-generated comment by a script] We noticed that this issue is targeted for M-65; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-65 label, otherwise remove Merge-TBD label. Thanks.
,
Feb 9 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by daalexbo...@gmail.com
, Feb 7 2018