User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release) Build ID: 20140716183446 Steps to reproduce: I was logging into my account at ATT.COM. Actual results: Firefox v31 built in Password Manager did not fill in user or password information. Expected results: P.M. should have filled in the information. I checked. P.M. has the information, but will not copy to the web page. I deleted the data, entered the info on the page, P.M. saved the data, but still not copy to login page. All settings for page look correct. NOTE: Add-on; AutoFill works on same page without any problem.
Similar bugs; Reported: 2010 https://bugzilla.mozilla.org/show_bug.cgi?id=618698 Autocomplete password manager doesnt work on some sites Assigned To: Nobody; OK to take it and work on it Reported: 2014 https://bugzilla.mozilla.org/show_bug.cgi?id=1046556 Login form autofill broken Note: Talks about multiple user / passwords same site
Hello Fred, Could you follow the instructions at https://wiki.mozilla.org/Firefox:Password_Manager_Debugging to turn on logging information and also look at the list of common reasons why passwords aren't autofilled. Could you also provide a direct link to the login page on att.com as sometimes there are multiple login pages on a website and some work while others don't.
Summary: Password Manager Not Work Some Web Sites → Password Manager doesn't autofill on att.com
Private message received from Col-el; https://support.mozilla.org/en-US/messages/read/19172 The web page www.att.com is using autocomplete=off on the input fields of the login form. You can see that if you right-click the name field and use Inspect Element to open the built-in Inspector. Current Firefox versions will offer remember the name and password, but likely still respect autocomplete=off and not autofill the name and password automatically.
I had thought autocomplete=off was ignored, but Col-el says autocomplete=off is ignored only when storing the password, not filling it in.
That's correct. Thanks for following-up.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.