Closed
Bug 513166
Opened 16 years ago
Closed 16 years ago
Remove "Warning Messages" settings button from Preferences --> Security
Categories
(Firefox :: Settings UI, defect)
Firefox
Settings UI
Tracking
()
RESOLVED
FIXED
Firefox 3.7a1
| Tracking | Status | |
|---|---|---|
| status1.9.1 | --- | wontfix |
People
(Reporter: Dolske, Assigned: ehsan.akhgari)
References
Details
(Keywords: useless-UI, Whiteboard: [killthem])
Attachments
(2 files)
|
67.34 KB,
image/png
|
Details | |
|
14.64 KB,
patch
|
dao
:
review+
benjamin
:
approval1.9.2-
|
Details | Diff | Splinter Review |
This was added as a way to undo (bring back) these warning messages. But, realistically, the warnings are annoying as heck and no one is going to use this UI. Uncommon prefs stuff that's taking up space should be removed.
| Reporter | ||
Updated•16 years ago
|
Whiteboard: [killthem]
Comment 1•16 years ago
|
||
Comment 2•16 years ago
|
||
And my axe.
Comment 3•16 years ago
|
||
What about overzealous anonymous/security users who browse cautiously?
Comment 4•16 years ago
|
||
(In reply to comment #3)
> What about overzealous anonymous/security users who browse cautiously?
I don't think we're talking about removing the prefs, we're talking about removing the dialog. In my conference/blogging/bug life, I actually come across a significant number of people who turn these back on, but there's a difference between supporting that... zeal, and promoting it in our preferences UI.
We protect our users' privacy - that's a top tier priority for Firefox - so in general I'm averse to taking away tools to help them specify their privacy preferences. But none of these dialogs are ones we'd WANT most users to turn on, because the nuisance would outweigh the benefit for any except the most diligent. If we don't want most users to change those prefs, it doesn't make sense to give them screen real estate, I agree.
Updated•16 years ago
|
Keywords: useless-UI
| Assignee | ||
Comment 5•16 years ago
|
||
Updated•16 years ago
|
Attachment #401615 -
Flags: review?(dao) → review+
| Assignee | ||
Comment 6•16 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
status1.9.1:
--- → wontfix
Flags: wanted-firefox3.6?
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.7a1
| Assignee | ||
Updated•16 years ago
|
Attachment #401615 -
Flags: approval1.9.2?
Comment 7•16 years ago
|
||
Comment on attachment 401615 [details] [diff] [review]
Patch
This has l10n changes, we can't take it as-is on the branch. We could probably take it without removing any of the strings.
Attachment #401615 -
Flags: approval1.9.2? → approval1.9.2-
Comment 8•16 years ago
|
||
(In reply to comment #4)
> We protect our users' privacy - that's a top tier priority for Firefox - so in
This is an untrue statement in my opinion. I wrote more in my comment on Faaborg blog: http://blog.mozilla.com/faaborg/2009/06/30/firefox-35-and-privacy/#comment-144055
Comment 9•15 years ago
|
||
A couple of Litmus and Mozmill tests are using this ui, which have to be updated now. Adding the litmus flag.
Flags: in-litmus?
Comment 10•15 years ago
|
||
https://litmus.mozilla.org/show_test.cgi?id=10538 had been disabled, so I think we are good in regard to Litmus here.
Flags: in-litmus? → in-litmus+
Description
•