New issue
Advanced search Search tips

Issue 920554 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Mac
Pri: 1
Type: Bug



Sign in to add a comment

New Password Form Parser is confused when the same field has different autocomplete and server predictions

Project Member Reported by dvadym@chromium.org, Jan 10

Issue description

On https://chromium-review.googlesource.com/c/chromium/src/+/1371813 some reorganizing of combination results from server and autocomplete attributes was done. As side effect, it may lead to the following:

Let we have password field P.
1.Server predication says that P is current-password.
2.Autocomplete attributes says that P is new-password.

As a result P is chosen as both new-password and current-password. 

It doesn't look that there are some problems with filling, but it might be a blocker for launching saving with the new parser in M-73.
 
Cc: dvadym@chromium.org
Owner: kolos@chromium.org
Status: Assigned (was: Untriaged)

Sign in to add a comment