On 3/16/2016 5:17 PM, Paul B. Gallagher wrote: > [email protected] wrote: > >> All this means that, as David mentioned, the password manager has no >> way to know that the password requested on the second page is in any >> way related to the username requested on the first page. It may be >> obvious to you that you're being asked for a username and password. >> It may be possible to do something that tries to work it out, but it >> probably wouldn't be completely reliable (and then people would >> probably complain about the odd time it doesn't get it right). Even >> determining that a given field is for a username, and not a search >> term or some other bit of information, is not necessarily easy. > > Logically, it should be possible. Suppose the password manager has a > record with > domain <whatever.com> > login "YourName" > password "StealMe" > When the user visits a page in <whatever.com> that contains a "login" > field, it should know to enter "YourName." When the user clicks and is > taken to another page in <whatever.com> that contains a "password" > field, it should know to enter "StealMe." > > I don't claim that password managers are designed that way. But > logically it should be possible. It's like going to 411.com and asking > for a person's phone number on one page and the same person's street > address on another page -- both pieces of data are contained in the same > record, and the database returns one piece in response to one input and > the other piece in response to the other input. >
That indeed is working for me. -- David E. Ross While many tributes to the late Supreme Court Associate Justice Antonin Scalia now fill the news media, his legacy was not necessarily positive. See my "What Price Order, Mr. Justice Scalia?" at <http://www.rossde.com/editorials/edtl_scalia_wrong.html>. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
