Open Bug 2087551 Opened 11 days ago Updated 7 days ago

Update documentation for clear-on-shutdown exceptions added in Fx154

Categories

(support.mozilla.org :: Knowledge Base Content, task)

Tracking

(Not tracked)

ASSIGNED

People

(Reporter: emz, Assigned: kiki)

References

Details

(Keywords: sumo-contributors)

Content access restriction: Is the content restricted to staff or under embargo (yes or no)?

No

Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each)

Firefox for Desktop (all OS)

Select the type of request.

KB content update/ new content

Please summarize the request, emphasizing any user-facing changes. Include historical context or background information if it helps users understand the new features or changes. [REQUIRED]

Traditionally "cookie" permissions were used to set exceptions from both anti-tracking and to exempt a site from being cleared on shutdown (if clearing on shutdown is enabled).

In https://bugzilla.mozilla.org/show_bug.cgi?id=1767271 we have split the permissions up. "cookie" permissions are used only for choosing if (and how) a site can set cookies and whether anti-tracking features apply for a site. We've added a new, dedicated "persist-data-on-shutdown" permission which exempts sites from shutdown clearing.

The current SUMO article currently does not cover this split and the updated UI that comes with it.

A contributor brought up the issue here: https://support.mozilla.org/en-US/forums/contributors/717795

Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]

Production Fx154

Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]

No

Please indicate if this is an on- or off-train release [REQUIRED]

On-train Fx154

What is the anticipated release date? [REQUIRED]

Already released

Does the content need to be published prior to the release date? If so, when? [REQUIRED]

N/A

Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]

Regular SUMO kb article (update). No special l10n handling.

Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

Implementation bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1767271
Contributor post describing the new behavior: https://support.mozilla.org/en-US/forums/contributors/717795

Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

The change followed established permission UI patterns so no design asset was produced.

Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

  1. Enable clearing data on shutdown on about:preferences#privacy -> History -> Customize History -> Clear history when Firefox closes
    2a. Add an exception for a site that shouldn't be cleared on shutdown via the "Manage Exceptions" button in "Customize History"
    2b. Visit a site e.g. example.com. Open the page info window with ctrl + i (or via the trust panel). Go to the permission tab and set "Keep site data when closing to "Always keep site data".

There is also the inverted state. When "Clear history when Firefox closes" is not enabled users can still set per-site permissions via pageinfo or preferences to only clear specific sites "Clear when closing".

The updated UI includes:

  • New "Manage Exceptions" button + dialog in "Customize History" preferences section
  • New entry in the Permissions tab of the Page Info window
  • Permission entries in the permissions panel (in the urlbar) when a site has a shutdown clearing exception set (Either positive or negative).

Does the content need approval before publishing? If yes, identify the one approver responsible for this task.

emz@mozilla.com

Taking this on me since it was initially brough by the contributor in the Community Discussion Forum. Tahnks for filing this request, emz!

Assignee: nobody → kelimutu
Status: NEW → ASSIGNED
You need to log in before you can comment on or make changes to this bug.