Closed
Bug 1765533
Opened 4 years ago
Closed 2 years ago
Issues with Clear Recent History
Categories
(Firefox :: Settings UI, defect, P3)
Firefox
Settings UI
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox123 | --- | fixed |
People
(Reporter: annevk, Unassigned)
References
(Blocks 1 open bug, )
Details
Attachments
(1 file)
|
232.77 KB,
image/jpeg
|
Details |
"Clear Recent History" under "Clear History..." under "History" has several issues:
- "Offline website data" is not a standalone thing and should not be listed as such. It's part of "Cookies and Site Data".
- "Cookies" is not a standalone thing and should not be listed as such. It's part of "Cookies and Site Data". (Though I could be convinced that we rename this category to just "Cookies" throughout, to roughly (accurately?) match European regulation.)
- I don't understand how "Active logins" is separate from "Cookies and Site Data". If you clear the latter, how could you still have an "Active login"?
Happy to split this bug up if desired once we have a shared understanding about next steps.
Comment 1•4 years ago
|
||
I created a mapping of the categories and the cleaners a while ago because I needed an overview. Might be useful here as well.
| Reporter | ||
Comment 2•4 years ago
|
||
Thanks hpeuckmann, that's great! That shows that "Active logins" maps to HTTP authentication which almost never maps to an actual login for most users (those use cookies). That should be grouped under "Cookies and Site Data" as well, in my opinion.
Comment 3•4 years ago
|
||
Setting to S3 because it seems like there's the potential for user confusion here.
Severity: -- → S3
Priority: -- → P3
Updated•4 years ago
|
Updated•3 years ago
|
Blocks: clear-data-revamp
Comment 4•2 years ago
|
||
Fixed in Bug 1861450 - Create new prefs and categories in Sanitizer for the new dialog box
- We merged active logins and offline website data into cookies and site data
- Cookies is now called cookies and site data
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
status-firefox123:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•