[meta] Clear Recent History / Forget button blind spots

NEW
Unassigned

Status

()

defect
P3
normal
5 years ago
18 days ago

People

(Reporter: dao, Unassigned)

Tracking

(Depends on 11 bugs, Blocks 1 bug, {meta, privacy})

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments)

Reporter

Description

5 years ago
Tracking bug for cases where Clear Recent History and the Forget button underperform, i.e. leave data behind that shouldn't be left behind. Theoretically this can be split into three categories:

1. site-specific data with or without timestamp left behind when clearing "everything" (no time range)

2. site-specific data with timestamp left behind when clearing a time range covering that timestamp

3. site-specific data without timestamp left behind when clearing a time range covering the time when that data was added, meaning that we're not leaking that the user definitely visited the site at that time, but we're still leaking that the user visited the site at all, which likely goes against the user's intent especially when the site was never visited before the selected time range

This bug explicitly does not track cases where data clearing is overzealous (e.g. bug 771630).
Reporter

Updated

5 years ago
Depends on: 527667
Reporter

Updated

5 years ago
Depends on: 518343
Reporter

Updated

5 years ago
Depends on: 901952
Reporter

Updated

5 years ago
Depends on: 973422
Reporter

Updated

5 years ago
Depends on: 463553
Reporter

Updated

5 years ago
Depends on: 481882
Reporter

Updated

5 years ago
Depends on: 607908
Reporter

Updated

5 years ago
Depends on: 652002
Reporter

Updated

5 years ago
Depends on: 652003
Reporter

Updated

5 years ago
Depends on: 1047098
Reporter

Comment 1

5 years ago
I prioritized the bugs currently tracked with the priority field. As a rule of thumb, I prioritized data persisted by web sites (e.g. indexedDB) higher than manually stored data that web sites can't directly access (e.g. cookie exceptions), and the lowest priority went to more obscure transient data and caches that go away automatically after some certain time or after a restart.
Depends on: 1252998
Depends on: 1253003
Depends on: 1253005
Depends on: 1253008
Depends on: 1253009
Depends on: 1253027
Depends on: 1253031
Depends on: 1401542
Depends on: 1367607

Comment 2

2 years ago
I believe the most concise and intuitive GUI for maintaining persistent user data is to enhance the Privacy settings section by creating a new item for each kind of persistence mechanism, resembling the Cookies privacy settings (see my attachments for visualization).

Comment 5

2 years ago
Version (a) adds a new paragraph to the Privacy settings section for LocalStorage and a new paragraph for IndexedDB.

Version (b) adds a tab strip - providing a tab for Cookies, LocalStorage, and IndexedDB. All sharing the same set of input elements within their tabs, respectively.
See Also: → 1422365
Depends on: 862465
Component: General → Data Sanitization
Priority: -- → P3
Product: Firefox → Toolkit
Summary: Clear Recent History / Forget button blind spots → [meta] Clear Recent History / Forget button blind spots
Depends on: 802220
No longer depends on: 1253008
Depends on: 475686
No longer depends on: 475686
Depends on: 1541450
Depends on: 1541885
Depends on: 1546296
Depends on: 1546295
See Also: → 1550317
Depends on: 606403
You need to log in before you can comment on or make changes to this bug.