Closed Bug 952143 Opened 12 years ago Closed 11 years ago

Expose signon.overrideAutocomplete in SeaMonkey preferences UI

Categories

(SeaMonkey :: Preferences, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: philip.chee, Unassigned)

References

(Blocks 1 open bug)

Details

(from bug 951981 comment #0) > Bug 425145 adds an about:config option, `signon.overrideAutocomplete`, which > when set to true allows the password manager to save passwords for pages > where the form/form elements have `autocomplete=false`. > > Can/should this be exposed in the preferences?
Blocks: FF2SM
Summary: Expose signon.autocompleteOverride in the preferences → Expose signon.autocompleteOverride in SeaMonkey preferences UI
Keywords: regression
Blocks: 486829
See Also: → 951981
Blocks: 973716
Whiteboard: [good first bug][lang=html][mentor=philip.chee]
Whiteboard: [good first bug][lang=html][mentor=philip.chee] → [good first bug][lang=xul][mentor=philip.chee]
Pref is probably going to be renamed and inverted in meaning, FYI (see blocking bug). Additionally, you might want to consider making it true (see bug 956906) for SM as well.
Depends on: 974742
I'd suggest for seamonkey to do the same as Firefox: Set the default to allow the password manager, and use the hidden pref for installations that disagree, and no UI.
Changing Summary to agree with the current name in about:config and bug 974742. I'm not taking sides as to whether or not to expose the pref, change its name and/or value, or whatever.
Summary: Expose signon.autocompleteOverride in SeaMonkey preferences UI → Expose signon.overrideAutocomplete in SeaMonkey preferences UI
I think we can say this has been fixed by bug 956906. Even if not strictly, but in purpose. The purpose of a pref UI would have been to allow a user to easily turn on the override and allow password fields to be filled in despite autocomplete="off". Now, that setting is the default, which not only allows what the UI would have allowed, but does it without any user action. Therefore, I mark this as a DUP. Adding UI now would serve the opposite purpose of being more restrictive. There is little point in that. So little point, in fact, that the pref was close to being removed entirely, because nobody could come up with a good usecase why you'd want to set this and still keep password manager on. See bug 956906 comment 49 ff. Please read this.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
This is NoT a DUP. It may possibly be a WONTFIX, but that necessitates further discussion.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
OK, then I propose WONTFIX, because the original purpose - giving users the ability to autofill passwords even when autocomplete=off - is fulfilled.
(In reply to Ben Bucksch (:BenB) from comment #6) > OK, then I propose WONTFIX, because the original purpose - giving users the > ability to autofill passwords even when autocomplete=off - is fulfilled. Sounds convincing.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → WONTFIX
Whiteboard: [good first bug][lang=xul][mentor=philip.chee]
You need to log in before you can comment on or make changes to this bug.