Closed Bug 23596 Opened 26 years ago Closed 26 years ago

[FEATURE] Redo Single Signon prefs

Categories

(SeaMonkey :: Passwords & Permissions, defect, P1)

Product:
SeaMonkey
Component:
Passwords & Permissions
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: bugzilla, Assigned: matt)

References

Details

(Whiteboard: [PDT+])

noticed this with today's builds (200001108)... 1. open up the Preferences dialog 2. select the Advanced category 3. the last checkbox is for "Automatically prefill usernames and passwords" expected: this checkbox should actually appear within the [new] Advanced > Wallet subcategory. result: the Wallet subcategory in Prefs lacks this checkbox. (i can understand it not going there since the Wallet subcat is a recent addition! :-)
When did this get added? I've never heard about a "wallet subcategory" nor do I see it on my build which is from 1-1-00. First of all, if the subcategory is called "wallet", then why should a single-signon pref go there? Single-signon and wallet are two different features. The wallet-server field perhaps should be there but not the single-signon checkbox. Perhaps the category should be renamed to be something more generic that would emcompass both -- such as autofill. Second, preference layouts are not my department. This would be dictated by German and implemented by Matt. Reassigning to German and cc-ing Matt.
Sarah's right there is wallet subcategory in the current builds under advanced. Steve's right, wallet is not a good term to encompass both functionalities. We should use AutoFill or SmartFill (or whatever tm the marketing folks would like us to use). Let's use 'Autofill' for now as a subcategory under advanced. And yes let's also add a checkbox above the button that lets you view the signons. The check box should say: [X] Enable Single Signon. Handing to matt for implementation, cc'ing ben.
Assignee: german → matt
Let's make sure we get it right this time. German, before Matt or Ben does this over again, can we get an outline or sreen dump or even a napkin sketch of exactly what you want?
Summary: Prefs: turning on SingleSignon should go under Adv > Wallet → [FEATURE] Redo Single Signon prefs
Target Milestone: M14
Yep, wee need this for beta 1. Matt, do you need help with this?
Keywords: beta1
Priority: P3 → P1
We're not doing autofill for beta, so we don't need to have autofill prefs for beta. Removing beta1 keyword.
Keywords: beta1
Putting on PDT+ radar for beta1.
Whiteboard: [PDT+]
Putting on PDT+ radar for beta1.
For beta I would leave most of what's there in the interest of time: simply rename the category to AutoFill (kevinyen OK?), put a check box inside the group "Single Signon" and label that checkbox "Enable Single Signon". I would also rename the first category: "AutFill for Web Forms". Also the first push button should be renamed to something like "View Stored Entries..." and the button in the signon group box should be renamed "View Stored Signons...". With the remaining space VeraH could add some explanatory text to each form fill and single signon. Also I would like VeraH to review what I just suggested and perform her wordsmithing magic to make sure we get it right. Therefore I re- assign to VeraH. VeraH once done please re-assign to Don.
Assignee: matt → verah
Autofill (aka Wallet, aka Form Fill) is OUT for beta1. Menu items need to be turned off. Michael's filing a bug to turn this stuff off. thx, kevin
Thanks Kevin for reminding me! OK than we should apply the upper part of the pref with the changes I outlined. The category term AutoFill is generic enough that it can hold whatever we can provide by beta 1. We could do these changes now and set the CSS display of this box to none, so none of the form fill part shows.
Accepting... I'll work on some wording ASAP.
Status: NEW → ASSIGNED
I think we should go with German's wording, except that I would like, if possible, to name this prefs category "Single Signon" instead of "AutoFill," for beta1. Both terms are new to users, and I'd rather not make them learn two new terms for what will appear to be (in the beta) a single feature. So here's how I'd do the UI text: Prefs category: "Single Signon" Title bar: "Single Signon" [instead of the current "Wallet"] Category name: "Single Signon" Checkbox: "Enable Single Signon" Explanatory text: "Single Signon stores your usernames and passwords for web sites that require you to log in, and enters them for you automatically when you visit those sites." Button: "View Stored Signons" Reassigning back to Don.
Assignee: verah → don
Status: ASSIGNED → NEW
Not sure I understand the sentence/phrase: "...make them learn two new terms for what will appear to be (in the beta) a single feature." Anyways, I believe we should stick with the agreed upon name "Password Manager" in beta 1 and beyond. The beta 1 name needs to be the same as post-beta 1 name, since this is how we're introducing the feature to millions of users and to reviewers (Reviewer's Guide). But as I mentioned first off, I'm not sure I understand the rationale to call it single signon (which doesn't connote the functionality as well as Password Manager does). Vera -- can you please elaborate? "Password Manager" until then. thx, kevin
Matt, how hard is this to do? Does it look possible for Tuesday? (probably not ...)
Assignee: don → matt
I didn't realize that "Password Manager" was a possibility. I certainly prefer that to "single signon." So here are my recommendations, revised: Prefs category: "Password Manager" Title bar: "Password Manager" [instead of the current "Wallet"] Category name: "Password Manager" Checkbox: "Enable Password Manager" Explanatory text: "Password Manager stores your usernames and passwords for web sites that require you to log in, and enters them for you automatically when you visit those sites." Button: "View Stored Passwords" Regarding teaching users two new terms -- German's proposal had both "single signon" and "autofill," both of which are new terms and probably don't mean anything specific to users encountering them for the first time. I was trying to eliminate one of them, "autofill," because if we don't have the automatic-filling-in-of-forms feature for beta1, I don't think we need to use this word that we've invented to describe it. And, perhaps by the time the feature is ready, we'll have thought of a better descriptor for it.
(just a note) Wallet != Single Signon. Wallet is more than a password manager, it stores values for other types of fields you fill in (e.g. address, full name, title etc). Single Signon is the one responsible for storing passwords. I think we should keep the two distinct to avoid naming conflicts and confusion.
To summarize, is the consensus then that we have one category for now 'Password Manager', and then later after beta 1 have a completely separate prefs category named 'Auto Fill' form filling?
Let's use "Password Manager" for beta1, since we won't have the form autofill feature at that time. After beta1 we can revisit this item and come up with a name that encompasses both "password management" and "autofill." (I have some suggestions.) If we can't find a name that we like that encompasses both, then we could keep them separate.
fixed
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
verification on linux and mac blocked by bug 28083.
Depends on: 28083
verif on linux w/opt comm bits, 2000022308.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.