Username/password not autofilled although stored
Reported by
mr.ber...@gmail.com,
Aug 11 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2826.0 Safari/537.36 Steps to reproduce the problem: 1. https://mc.manuscriptcentral.com/tns-ieee 2. Have user account with that site, and login details stored in Chrome 3. Note the key symbol in the omnibox, which on click shows a bubble with my two accounts emails and two sets of stars (*****...) to indicate that login details ARE stored. What is the expected behavior? Upon loading the site, or double-clicking the "email" input field, I expect an autofill dropdown with my two accounts. What went wrong? Nothing happens. I can login manually just fine, but that's not what I want. Did this work before? N/A Chrome version: 54.0.2826.0 Channel: canary OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0 Same on 52.0.2743.116 m (64-bit)
,
Aug 12 2016
Navigating to site displays the error " This is a notice to alert you that we will conduct scheduled maintenance on ScholarOne Manuscripts v4.19 on August 17, 2016. " Could you please provide the test credentials to test this further.
,
Aug 12 2016
The "error" you talk about is a simple announcement about future maintenance, the site is fully functional as of today (August 17 is next Wednesday). Registration is open on the web site, so I created an account for you: "mc@mailinator.com", "thanks12"
,
Aug 19 2016
Thank you for providing more feedback. Adding requester "tkonchada@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 30 2016
This may be a duplicate of Issue 627497 .
,
Sep 7 2016
It looks like this is working in 53.0.2785.89 (stable) and 55.0.2853.0 canary. I wonder if v54 still has this issue (can't test this).
,
Mar 13 2017
Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919
,
Sep 9 2017
,
Oct 23 2017
Please comment here, e-mail me or file a new bug if this issue is still present in the current Chrome. Given #6 and the report of this working in 55, I'm closing this report for now. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mr.ber...@gmail.com
, Aug 11 2016