password for fairfaxcu.org does not autofill |
|||||
Issue descriptionApp Version:59.0.3054.0 iOS Version: iOs10.3.1 Device: iPhone7 URL: fairfaxcu.org Steps to reproduce: 1. On desktop (signed in for sync) go to fairfaxcu.org and login, opt to save the u/p 2. On ios, open Chrome (signed in for sync), go to fairfaxcu.org Observed results: Note that username field is on homepage, and is not autofilled. It is also not autofilled on desktop. Fill in username, go to the next screen. Password is also not filled in. Expected results: Password is never filled in. Note on desktop at least the password gets filled in. Number of times you were able to reproduce: 5/5 Bug reproducible after clean install:Yes Bug reproducible after clearing cache and cookies:Yes Observed behavior in Chrome Mobile on Android: n/a Check for similar behavior on Firefox/Safari: n/a Bug reproducible on current stable build (App Version, iOS Version): Yes M57 Bug reproducible on the current beta channel build (App Version, iOS Version): Yes M58
,
Apr 5 2017
Hi vabr@ , melandory@ could you please take a look.
,
Apr 6 2017
As explained to lindsayw@ in an e-mail, I am moving these bugs to our TODO list, and reducing some unnecessary noise they cause.
,
Apr 16 2017
Let us track only filling the password in this bug. As described in #0, the page separates username from password by one navigation. On the username-only part, Chrome's autocomplete feature kicks in and offers to fill the username on demand. On the password-only part, there is no username input field any more; short of parsing and understanding the plain text of the page, Chrome has no way to understand what the username is and to associate it with the stored password. Hence the user can only store one password for the page, and it will be associated with "No username". This is caused by the poor security design of the page, which is thankfully an edge case. Fixing the behaviour for this edge case would involve unreasonable effort and complexity on Chrome's site, so we won't do that.
,
Apr 5 2018
Sounds like a WontFix then. Please feel free to re-open if you think otherwise. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by linds...@chromium.org
, Apr 5 2017