User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Firefox/1.0.1 Websites with logins do not automatically log on when a page is loaded when Firefox is started. For example, sites such as the New York Times (http://www.nytimes.com) and Slashdot (http://slashdot.org) with free logins will load, but the login will not authenticate. Password manager will fill in the user name and password, but the user has to click login to send the login request. On sites necessitating passwords to access, the user is forced to login before the sites will grant access (including the Wall St. Journal site http://online.wsj.com/home/us). Reproducible: Always Steps to Reproduce: 1. Go to New York Times (http://www.nytimes.com) 2. Login using free registration 3. When prompted, save using Password Manager 4. Quit Firefox. Restart. 5. Go to NY Times site Actual Results: Website loads, but login is not submitted. This means that when the user attempts to open a story, they are prompted for their login. The password manager fills in the username and password, but the user still must submit the form. Expected Results: The site should have loaded already logged on under the saved username. The bug does not occur using Firefox in MS Windows XP, nor does it occur using Mozilla on OS X. It has occured thus far on Macs in every version of Firefox I've run on OS X.
Does this have anything to do with users with disabilities, such as users with visual or physical impairments?
When I entered the bug it was listed under Password Manager, not Disability Access. I must have inadvertently changed the component. It was intended to fall under Password Manager. Can someone sufficiently empowered reassign it? Sorry for the inconvenience.
Is this a dupe of Bug 221634 [pwd-mngr] password manager needs to fill in forms before the page finishes loading?
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.