On 5/18/11 9:50 PM, Stanimir Stamenkov wrote: > Wed, 18 May 2011 19:35:32 -0700, /David E. Ross/: > >> Reverting back to SM 2.0.14 and then reinstalling SM 2.1RC1, I got >> things to work a little better. With your two HTML pages, I put a user >> ID in username.html and got password.html. When I input a password in >> password.html, I was actually able to save it. >> >> Later, I terminated SeaMonkey and then relaunched it. I again tried >> your two HTML pages. Yes, the password had been saved and was available >> from Password Manager. >> >> This raises a question about why Password Manager cannot provide a saved >> password for other split logins. > > If you could provide URL to an example of split login may be we > could find more? >
The only two where I have had a problem are: <https://personal.vanguard.com/us/home> <https://www.caloaks.com/> However, both of these are for financial institutions that require you have a financial account before you can obtain a login. I believe that both of these now disable the saving of passwords, but Password Manager is supposed to handle such cases if passwords were already saved. I suspect that this specific capability is what is broken: handling SAVED passwords on a SPLIT LOGIN where the Web page DISABLES the saving of passwords. I login to the Web sites of other financial institutions that I know now disable the saving of passwords. The logins are not split, and Password Manager enters the user ID and password appropriately. -- David E. Ross <http://www.rossde.com/> On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
