Password Preferences are in the wrong place.

NEW
Unassigned

Status

Camino Graveyard
Preferences
--
minor
15 years ago
10 years ago

People

(Reporter: Brad Kemper, Unassigned)

Tracking

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021209 Chimera/0.6+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021209 Chimera/0.6+

Passwords are a security feature. So why are their preferences not stored under
the "security" icon in Mozilla's preferences? I suggest that "Cookies" (or
"Privacy"), "Passwords", and "Warnings" be three tabs in the "Security"
preferences. It would be simpler and easier than making people try to remember
which of those three things were in "Privacy" and which were in "Security".

Reproducible: Always

Steps to Reproduce:
(Reporter)

Comment 1

15 years ago
*** Bug 184558 has been marked as a duplicate of this bug. ***

Updated

15 years ago
Summary: Password Prefferences are in the wrong place. → Password Preferences are in the wrong place.
(Reporter)

Comment 2

15 years ago
know what I mean?
(Reporter)

Comment 3

15 years ago
Well, that's what I think anyway. What do you think, Brad?
(Reporter)

Comment 4

15 years ago
Oh, I concur completely. It was awfully smart of you to point that out.
(Reporter)

Comment 5

15 years ago
Why, thank you. It sure is quiet in here.

Comment 6

15 years ago
We're still seeking the ultimate prefs layout.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Time to revisit this bug.

Comment 8

13 years ago
Everyone agree?
Priority: -- → P3
Target Milestone: --- → Camino1.0
I agree. Should be as follows with three tabs:

Security Panel
 - Cookies
 - Passwords
 - Warnings

This would also make the Appearance pane look less out of place with it's tabs.
Aside from the prefpane name, I agree.  Cookies aren't a security function. 
Passwords could go either way.  (DeerPark has history, forms, passwords,
download history, cookies, and cache in its Privacy pane.) 

Protection? 

Simon, when we add all of those certificate-related features, would anything go
under this new "security" prefpane?  Inspecting stored certificates?

Comment 11

13 years ago
(In reply to comment #10)
> Simon, when we add all of those certificate-related features, would anything go
> under this new "security" prefpane?  Inspecting stored certificates?

Yes, although it's probably just one button ("Show Certificates").
i'm just loathe to add tabs to the panes. users have a hell of a time finding
things inside pref panes with tabs.
(Reporter)

Comment 13

13 years ago
(In reply to comment #10)
> Aside from the prefpane name, I agree.  Cookies aren't a security function. 

Well, restricting and deleting cookies is a privacy issue, and privacy is something that people want to 
keep secure. So I think either "Privacy" or "Cookies" works well for the tab name inside a "Security" 
preference pane.
(Reporter)

Comment 14

13 years ago
(In reply to comment #12)
> i'm just loathe to add tabs to the panes. users have a hell of a time finding
> things inside pref panes with tabs.

"Navigation" and "Appearance" both have tabs, and it is a standard interface element, so I don't see why 
we should start avoiding them now. Aren't we trying to let this creature take advantage of Mac ways of 
doing things?
"Navigation" got busted up a long, long time ago, and IMO "Appearance" should
get busted up into "Appearance" and "Fonts", too.  That would give us
much-needed flexibility in reworking the "Fonts" pane so that there aren't those
hideous selects for the "Advanced" prefs.  (And it was wierd being the only pane
with tabs).

If passwords don't make sense under "Privacy", then bust "Privacy" into
"Cookies" and "Passwords", too.

But if we bust both of them, we'd need to either increase the default width of
the prefs window (and thus re-layout every pane) so that they all show in the
toolbar without the overflow menu by default or change back to the old "grouped"
prefs layout (a la System Prefs under 10.3).
-> 1.1
Target Milestone: Camino1.0 → Camino1.1
QA Contact: bugzilla → preferences
Target Milestone: Camino1.1 → Camino2.0

Updated

10 years ago
Assignee: sfraser_bugs → nobody
Status: ASSIGNED → NEW
Priority: P3 → --
Target Milestone: Camino2.0 → ---
You need to log in before you can comment on or make changes to this bug.