| Key: |
SAK-5372
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Won't Fix
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Stephen Marquard
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
None
|
|
Image Attachments:
|
|
|
Environment:
|
nightly2 (Oracle), client browser Firefox 1.5.0.3 on Win XP SP2
|
|
| 2.6.x Status: |
None
|
| 2.5.x Status: |
None
|
| 2.4.x Status: |
None
|
|
Using Firefox (tested with 1.5.0.3), if you have logged in to a Sakai site with say admin/admin, and allowed Firefox to remember that username/password combination when you login, then go to Administration Workspace / Users / New User:
- The 'userid' and 'create new password' fields are prepopulated by Firefox
- If you click 'Cancel', FF asks whether you want to save the stored password.
I don't know exactly what in the HTML prompts Firefox to prepopulate the fields, and/or what triggers the dialog on Cancel, but it would be desireable to suppress both of these behaviours in FF.
IE has different behaviour, so this is not a problem in IE.
|
|
Description
|
Using Firefox (tested with 1.5.0.3), if you have logged in to a Sakai site with say admin/admin, and allowed Firefox to remember that username/password combination when you login, then go to Administration Workspace / Users / New User:
- The 'userid' and 'create new password' fields are prepopulated by Firefox
- If you click 'Cancel', FF asks whether you want to save the stored password.
I don't know exactly what in the HTML prompts Firefox to prepopulate the fields, and/or what triggers the dialog on Cancel, but it would be desireable to suppress both of these behaviours in FF.
IE has different behaviour, so this is not a problem in IE.
|
Show » |
|
Firefox autocomplete problems with Add New User
There is a remaining strange issue with this, when the names are changed. If we do a successful edit, it works fine, with no pre-populating of the form fields for "admin" and the password, and no asking if we want to save a new admin password on submit. But if we have an error in the form, leaving out a password field, for instance, then we get the "do you want to save this new admin password", even though the eid field (called "ceid" in this test) has some other user id.
I'll revisit after 2.2.