New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 835015 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Credential autofill lingers after filling

Project Member Reported by elawrence@chromium.org, Apr 19 2018

Issue description

Chrome Version: 68.0.3400.0 
OS: Windows 10

What steps will reproduce the problem?
(1) Enable Fill-on-Account-Select (chrome://flags#fill-on-account-select)
(2) Go to https://fiddler.ideas.aha.io and try to comment on a suggestion
(3) Go through the authentication flow, picking username and then password. Submit the comment.

EXPECT: Autofill popup disappears
ACTUAL: Autofill popup remains

Note: The fact that the popup appears in the wrong location may be dupe of Issue 833432.
 
LingeringAutoFillpopup.png
59.7 KB View Download

Comment 1 by battre@chromium.org, Apr 20 2018

Labels: Needs-Bisect

Comment 2 by battre@chromium.org, Apr 20 2018

Cc: ftirelo@chromium.org se...@chromium.org
Components: UI>Browser>Autofill
Status: Available (was: Untriaged)

Comment 3 by ma...@chromium.org, Apr 20 2018

Owner: tmartino@chromium.org
Increased padding makes me think this is a Views popup
Does the behavior change if you enable/disable chrome://flags/#enable-autofill-native-dropdown-views ?
This repros with chrome://flags/#enable-autofill-native-dropdown-views both enabled and disabled.
Owner: battre@chromium.org
Reasigning to battre@ for triage. it looks very similar to crbug.com/833432
Labels: -Type-Bug -Pri-3 -Needs-Bisect RegressedIn-62 Target-67 Needs-Triage-M68 M-68 Target-66 FoundIn-66 FoundIn-67 Triaged-ET Target-68 hasbisect Pri-1 Type-Bug-Regression
Status: Assigned (was: Available)
Able to reproduce the issue on Windows 10 using chrome reported version #68.0.3400.0. Issue is not seen in OS-mac and OS-Linux.

Bisect Information:
=====================
Good build: 62.0.3196.0
Bad Build : 62.0.3197.0

Change Log URL: (from omahaproxy)
https://www.google.com/url?q=https://chromium.googlesource.com/chromium/src/%2Blog/62.0.3196.0..62.0.3197.0?pretty%3Dfuller%26n%3D10000&sa=D&source=hangouts&ust=1524560203174000&usg=AFQjCNHNk_0g3DsMq2oNwlx9P2-VCU6Dqw
Not: Providing CL from omahaproxy as the bisect script invoked chrome builds that crashed.

From the above change log suspecting below change
Change-Id: I85737dbe848820117dea01c7944bb139454e751b
Reviewed-on: https://chromium-review.googlesource.com/635124

battre@ - 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.

Thanks...!!

Comment 8 by battre@chromium.org, Apr 23 2018

Cc: battre@chromium.org
Owner: krajshree@chromium.org
No this CL is not related. It does not touch any UI. The window is still pretty big. Could you do a code bisect for us?

Comment 9 by battre@chromium.org, Apr 23 2018

BTW: I think that the problem exists already at 62.0.3196.0. I am not sure the regression window is correct, yet.
I noticed today that I seem to be getting a similar popup immediately upon loading the NYTimes homepage; there doesn't appear to be a visible login field anywhere.
NyTimes.png
182 KB View Download

Sign in to add a comment