Closed Bug 57923 Opened 24 years ago Closed 22 years ago

fills in same info for every field with same name on entire site

Categories

(SeaMonkey :: Passwords & Permissions, defect)

x86
Windows 98
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 153986

People

(Reporter: mishreal, Assigned: morse)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/4.73 [en] (Win98; I)
BuildID:    2000102304

Mozilla will fill in the same info for a form on every page of the site if the 
form field names are the same. If you input 2 usernames, you get an annoying 
pop-up box asking you to select a name on every page with a form. It should save 
passwords per page not per site.

Reproducible: Always
Steps to Reproduce:
1.sign up for a forum account - Save the password for the site
2.load the front page
3.name is filled in on "freecounter login"
4.visit http://www.plebian.com/settlers
5.click "post news" - name is also filled in there
Just a nit, but I believe you meant the component to be single-signon and not 
autofill.  Single signon has to do with the password manager which is what you 
are describing whereas autofill has to do with the form manager.  I own them 
both but I'm modifying the component here for clarity.  I believe that bug 57910 
might be a dup of this one, although I dismissed it as invalid because it was 
marked autofill and I interpreted it as such.
Status: UNCONFIRMED → NEW
Component: Autofill → Single Signon
Ever confirmed: true
Your point is well taken.  This was done by design.  When I first implemented 
it, I tried to use it at vanguard.com and discovered that I was being routed to 
different servers randomly each time I logged on.  So I made the identification 
be to the host (www.vanguart.com) and not include the path or port numbers.  
This was for convenience.

I was well aware that this could lead to the opposite problem -- i.e., two 
entirely different forms (perhaps from different companies) both under the same 
host would each get the others saved log-in.  So this was a design trade-off.  
The first time the user encounters such a situation he could save both 
username/password pairs and then on future visits to either login form he would 
be presented with a list from which to chose the saved login that he wants to 
use.

Therefore marking this as won't fix.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
Per morse's comments, I'm marking verified
Status: RESOLVED → VERIFIED
reopening to dupe properly. this should have been done the first time with one
of the existing bugs.
Status: VERIFIED → REOPENED
Resolution: WONTFIX → ---

*** This bug has been marked as a duplicate of 153986 ***
Status: REOPENED → RESOLVED
Closed: 24 years ago22 years ago
Resolution: --- → DUPLICATE
I think this one was duped accidentally.  Sites with two types of logins (post
news and post comments, for example) should use different field names for the
two forms to avoid confusing password manager.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Priority: P3 → --
No, I don't think that dup was accidental.  Bug 153986 (Improve password manager
heuristic so it doesn't break sites) is exactly the problem we are running into
here.  The idea is that we might be able to improve the heuristic so that it
works correctly on more and more sites.

*** This bug has been marked as a duplicate of 153986 ***
Status: REOPENED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.