"Clear cookies and site data on exit" also clears Exception / Allow lists
Categories
(Toolkit :: Data Sanitization, defect)
Tracking
()
People
(Reporter: postmaster, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
|
17.81 KB,
image/png
|
Details |
Steps to reproduce:
- In the Settings, go to Privacy & Security and scroll down to Browsing data
- Click Manage exceptions and add, say, https://bugzilla.mozilla.org/
- Check the Clear site data and cookies on exit box
- Open https://bugzilla.mozilla.org/ and log in
- Close and reopen Firefox
Actual results:
All cookies are gone, though https://bugzilla.mozilla.org/ was in the allow list
Expected results:
Cookies from the allow list should have remained.
That was the behaviour up until "recently".
Comment 1•2 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Data Sanitization' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•2 months ago
|
Comment 2•2 months ago
|
||
:emz, since you are the author of the regressor, bug 1767271, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 3•2 months ago
•
|
||
see emz's pic and subsequent comment (pasted below) here https://bugzilla.mozilla.org/show_bug.cgi?id=2065902#c12
clearing cookies and site data exceptions USED to be under "Browsing data" (in FF153 or lower). In FF154+ this is should only be used to allow or block cookie access for websites.
In FF154+ a migration will run once to copy those existing exceptions to a new location - that location is under "History" (see emz's pic)
Comment 4•2 months ago
•
|
||
Thanks Thorin! We should have communicated this change better. Quite a few folks are confused.
Comment 5•2 months ago
|
||
Yeah, it's all a bit orthogonal - what's sanitized is under history, but exceptions are specifically for browsing data. Here's my 2 cents - the current FF155 browsing data>manage exceptions (which are cookie permissions) is sammiched between three clear.. items, which isn't ideal
Move permissions up under data usage and away from any mention of clearing
Move sanitizing exceptions under the checkbox because the exceptions are specifically only cookies/sitedata (and not other items in browsing data such as cache, form info). Note that manual sanitizing doesn't respect exceptions [1], hence keeping it away from :fire: Clear browsing data
That make 3 clear (pun intended) Browsing data sub-sections
- usage + permissions to use
- clearing
- sanitizing on close
What do you think? IANAE on design or UX, but you wouldn't even need any more translations/code, just move the items around: ni emz (sorry for the noise)
[1] see Bug 1769327 - that was for cpd (ctrl-alt-del etc), and it's been a while so not 100% sure the UI for Clear browsing data respects exceptions
| Reporter | ||
Comment 6•2 months ago
|
||
First and foremost, thanks everyone for your constructive comments and explanations.
I can confirm: using the "clear on exit" from the history section (with exceptions there) and unchecking "clear on exit" from the cookies section works exactly as expected.
With this in mind, indeed some UI alignment could be helpful:
- The "clear on exit" in the cookies section seems superflous, it could be removed
- The naming of the "clear on exit" button in history could be more specific so people naturally understand what else it can clear on exit (not "just" history)
=> That's linked to a greater question: the clearing of current cookies and cache can also be done via the history section.
I have my solution, so having my bug as "RESOLVED" is perfect. Looking forward to UI improvements of course, though I believe only few use their browsers this way (i.e., "browse unlimited" but then delete all cookies and storage except for the few sites to be always kept).
Updated•2 months ago
|
Description
•