Regression:Unwanted Update password bubble is seen after clicking on Login by using password from password generation.
Reported by
shruti.j...@etouch.net,
Nov 2 2017
|
||
Issue descriptionChrome Version:64.0.3256.0 b0a2dcae908c0df01ffa219ef4b48b5decc14f4c-refs/heads/master@{#513348}(32/64-bit) OS: Win(7,8,10), Mac(10.12.6) and Linux(14.04 LTS). Pre-condition:Sign-in Chrome and enable password generation flag. Test URL: fb.com Steps to reproduce: 1.Launch chrome and navigate to above URL. 2.Select a password from password generation suggestions and click on Login button. 3.Navigate back and erase the password then again select a new suggestion from password generation and again click on Login button and observe. Actual Result:Unwanted Update password bubble is seen after clicking on Login by using password from password generation. Expected Result:Unwanted Update password bubble should not be seen after clicking on Login by using password from password generation. This is regression issue broken in ‘M-63’ and below per-revision bisect result Using the per-revision bisect providing the bisect results, Good Build: 63.0.3238.0(Revision:508209). Bad Build: 63.0.3239.0(Revision:508578). You are probably looking for a change made after 508363 (known good), but no later than 508364 (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/0502f56e5ba44fdd5c10ffaeb4f863979c692efe..455aa605ebe316e720bda82dea55e31f55ba9c8b Suspect: https://chromium.googlesource.com/chromium/src/+/455aa605ebe316e720bda82dea55e31f55ba9c8b @kolos: 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.
,
Nov 6 2017
M63 Stable promotion is coming soon and your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge to M63 ASAP. Thank you.
,
Nov 7 2017
Works as expected. I agree it is a bit weird that Chrome updates a credential when a user clicked at another form. The trick is that "Login" button is not connected to any form, it just triggers in-page navigation. Chrome provisionally save a form where the user made last change (i.e. sign-up form). Then Chrome sees in-page navigation and sees that sign-up form disappeared which means successful login. Thus, Chrome offers to update the password. I believe this change https://chromium.googlesource.com/chromium/src/+/455aa605ebe316e720bda82dea55e31f55ba9c8b didn't affect on it. The use case is quite uncommon. I don't think this is a release blocker. |
||
►
Sign in to add a comment |
||
Comment 1 by rbasuvula@chromium.org
, Nov 2 2017