Just as other security prompts have options to never ask again, the password save prompt should have more than just "Never for this site." There should be a checkbox to always perform the action for all sites, that is, always save or don't save (I'm particularly interested in the last one without having to go into preferences to turn it off). Casual users that always select the same answer for all sites won't even know where to go to set this and it will just become an annoyance to them.
I'm thinking that this is a misfeature. A global setting like you suggest for that belongs in preferences. Also, this is a safety feature. If I sit down at someone's computer where they are running a mozilla client, I want to know that it won't go off storing passwords at random. As for disabling, I guess that could be done, but unchecking "remember passwords" doesn't seem like something too hard to do. Anyway I'd say that this should be either severity enhancement or wontfix
That is why I said it should be a checkbox. Turning saving OFF, as I said is my bigger concern, but we may as well offer all possibilities. Anyway, we store cookies without asking each time by default, which stores passwords or their derivatives a lot of the time. Remember, this is supposed to be convenient... IE is convenient, it doesn't ask you for each site, it only has a global setting. Mozilla offering both choices just makes it more compelling.
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → EXPIRED
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: EXPIRED → ---
You need to log in before you can comment on or make changes to this bug.