Closed
Bug 33613
Opened 24 years ago
Closed 24 years ago
Single Signon not saving info
Categories
(SeaMonkey :: Passwords & Permissions, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
M15
People
(Reporter: gerv, Assigned: morse)
References
()
Details
(Keywords: regression)
From Bugzilla Helper: User-Agent: Mozilla/4.7 [en] (Win95; U) BuildID: 20000328 Single signon is broken multiple ways. There are several problems, best described in relation to the relevant testcases from http://www.mozilla.org/quality/help/smoketests/. Test case B34 (single signon, username and password). You are asked if you want to save the signon, and for a master password. However, if you quit and reload the page, it does not ask you for a password in order to fill in the dialog. If you "store" the signon using an earlier version, and then visit the page in 20000328, it does. This indicates a problem in saving the data. B33 - Amazon form filling. You can fill in the data in the normal way, and a check of the wallet shows it has been stored. However, attempting a fill (after a shutdown) leads to "enter master password" dialog, as if data had not been saved. If you enter one, it says "There are no fields that can be prefilled". As a side note, it's possible to get two or more copies of many of the single signon password dialogs, which is Bad. Reproducible: Always
Reporter | ||
Comment 1•24 years ago
|
||
Adding regression keyword. This regressed between 20000327 and 20000328. Gerv
Keywords: regression
Assignee | ||
Comment 2•24 years ago
|
||
The two copies of the master password dialog is a consequence of bug 25684 (lack of modal dialogs). The other symptoms, especially if they are regressions that just occured to day, disturb me. I'll pull a tree from today and test it out.
Status: NEW → ASSIGNED
Target Milestone: --- → M15
Assignee | ||
Comment 3•24 years ago
|
||
Am unable to reproduce first item. Using a tree that I just pulled, here are the steps that I performed: 1. Went to http://people.netscape.com/paulmac/login.html 2. Entered the indicated username and password 3. Pressed LOGIN 4. Received dialog asking if I wanted to save password 5. Replies YES 6. Received dialog asking for master password 7. Entered master password 8. Closed the browser 9. Re-entered the browsser 10. Went back to http://people.netscape.com/paulmac/login.html 11. Received dialog asking for master password 12. Entered master password 13. Username and password became prefilled Is this indeed the correct sequence of steps to demonstrate the problem. If so, then it works-for-me. Did not test out the second item since I presume that I will get the same result. In any case, two different bugs should not be put into a single report but should each go into there own report. Please retest and re-open this report if you are still seeing the problem. And, if so, please give a detailed set of steps that you performed. Also indicate if you used a fresh profile or relied on some pre-existing profile.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 4•24 years ago
|
||
I have followed the steps you gave and still see this problem on 20000328, the build it was discovered on (cross platform). I filed both bugs in the same bug for two reasons: 1) We were in the middle of smoketesting, under pressure to get the tree open 2) It looks like they have the same root cause - info not saved I will make sure this gets thoroughly tested on the smoketest tomorrow am. If there is still a problem I will reopen the bug. Gerv
Assignee | ||
Comment 5•24 years ago
|
||
If you still see the problem, then please do the following: - Determine if it fails for new profile or only for an existing one - If it works fine with a new profile but not with an existing one, the zip up the entire profile and attach it to the bug report.
Reporter | ||
Comment 6•24 years ago
|
||
WORKSFORME in 20000329. I hear there was a short regression where no prefs info was saved at all. That's probably what caused it. Gerv
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•