Regression: Page got stuck and does not navigated to google.com after siging out from NTP.
Reported by
db...@etouch.net,
Apr 19 2018
|
|||||||||
Issue descriptionChrome Version: 68.0.3400.0 Revision 9f775bf70a07668811dfc3b55bbd2e5f9c910fd0-refs/heads/master@{#551875}(32/64 bit) OS: Windows(7,8,8.1,10), Mac(10.12.6,10.13.1,10.13.5) What steps will reproduce the problem? (1) Launch chrome, navigate to gmail.com sign in with valid crendentials. (2) Now open NTP and click on profile icon button and select sign out option. (3) Observe page. Actual: Page got stuck and does not navigated to google.com after siging out. Expected: Page should navigated to google.com after siging out. This is a regression issue, broken in 'M65', provinding bisect using bisect per revision": Good Build: 65.0.3295.0 Bad Build: 65.0.3296.0 You are probably looking for a change made after 524528 (known good), but no later than 524529 (first known bad). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/24abf78274e01a17c4f0a4c8cc18e55720f3b3b9..3b60933b099bba43823b2c5cbdbe7c3f2e90ae68 Ssupect: https://chromium.googlesource.com/chromium/src/+/3b60933b099bba43823b2c5cbdbe7c3f2e90ae68 @<alexmos: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Note: Issue is also seen on M66 Stable build #66.0.3359.117, M66 Beta build #66.0.3359.117 and M67 Dev build #67.0.3393.4
,
Apr 20 2018
Assigning to Sabine as the new owner for sign-in and bumping down the priority. I'd be surprised if this were caused by a change in Chrome. Either way, I agree with Alex's assessment; this doesn't feel like a bug, it seems like the "new" behavior is better. Sabine can decide how to prioritize and triage. I would just mark it as WontFix.
,
Apr 20 2018
+ramyan (new NTP owner) FYI It seems plausible that this could be caused by sign-in isolation somehow, but if not, it might as well be a change to the OneGoogleBar. Anyway, I agree that the new behavior seems like an improvement, let's keep it :) One minor bug I noticed in the "Actual" video: After the sign-out, the actual NTP URL shows up in the tab bar rather than "New Tab".
,
Apr 24 2018
,
May 25 2018
--Chrome Identity automated triaging-- This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 26 2018
+Yana FYI I agree that staying on the NTP after signing out from the NTP would be fine behaviour. However, this is not what I observed in the latest M68 Beta (see attached screencast), where 'Continue' forwards to google.com. The tab bar shows the correct site title ("Google"), instead of the URL, so I don't think there's any NTP work here. Since this is no longer a regression, perhaps the bug can be closed?
,
Aug 2
,
Sep 3
--Chrome Identity automated triaging-- This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 16
Removing older targets for NTP. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by alex...@chromium.org
, Apr 20 2018