Open Bug 1441861 Opened 7 years ago Updated 2 years ago

Reorganize "Settings for Clearing History" to improve intuitiveness

Categories

(Firefox :: Settings UI, enhancement, P3)

enhancement

Tracking

()

REOPENED
Tracking Status
firefox60 --- affected

People

(Reporter: from_bugzilla3, Unassigned)

References

(Blocks 1 open bug)

Details

The organization of the "Settings for Clearing History" dialog is currently less than ideal in two ways: 1. "Cookies" aren't really "History" in the same sense as the other entries in the group. First, while the way they are used means they often serve in that role, they are conceptually just a more limited precursor to mechanisms unarguably intended for allowing web applications to store client-side state. Second, it's possible for a site to use mechanisms which are intended to store bulk data for "History" purposes. 2. The current placement of "Site Preferences" can lead one's intuition to assume that it refers to preferences set by the website, rather than preferences set by the browser ABOUT the website. (This led me to accidentally configure my browser to be less protective of my privacy when I thought I was doing the opposite, by rendering per-site cookie rules unusable. A misconception which led me to file bug 1439261.) My suggested solution is to do one or both of the following: 1. Rename "Site Preferences" to "Site-specific Browser Preferences" 2. Replace the current "History" and "Data" groupings with "Browser Data" and "Site Data"... an organization which I believe to be more meaningful. (My recommendation would be to do the latter, as "Site Preferences" should be unambiguous when placed within a "Browser Data" group.)
Blocks: storage-v2
Severity: normal → enhancement
Version: 59 Branch → Trunk
Component: Untriaged → Preferences
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
My primary motivation in posting this was actually to resolve the ambiguity of the "Site Preferences" checkbox under "Settings for Clearing History". (As-is, it led me to configure a behaviour completely opposite to what I'd intended.) I don't see any mention of that in bug 1432743. Is there a more appropriate bug this could be duped to?
Yeah I don't think this is a dupe, it's about the "Clear History" dialog, which we did not improve (yet).
Status: RESOLVED → REOPENED
Ever confirmed: true
Priority: -- → P3
Resolution: DUPLICATE → ---
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.