Policy: Clear all data when the browser exits

VERIFIED FIXED in Firefox 60

Status

()

defect
P1
normal
VERIFIED FIXED
2 years ago
Last year

People

(Reporter: Felipe, Assigned: mkaply)

Tracking

Trunk
Firefox 61
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox59 unaffected, firefox60+ verified, firefox61 verified)

Details

Attachments

(1 attachment)

There's the Always on Private browsing (Preferences -> Never remember History) and this is probably what this request is about. 

(There's also the pref privacy.sanitize.sanitizeOnShutdown, but it shows UI to the user upon exit, which is probably not desired)
Assignee

Comment 1

Last year
We can do it ourselves using Sanitizer.sanitize

https://searchfox.org/mozilla-central/source/browser/modules/Sanitizer.jsm#931

The ones that default to true are:

cache
cookies
downloads
formdata
history
openWindows
sessions

The ones that default to false are:

offlineApps
siteSettings

Not sure how to write a test for this though...
Isn't it easier to just use the browser.privatebrowsing.autostart pref?
Comment hidden (mozreview-request)
Assignee

Updated

Last year
Assignee: nobody → mozilla
Status: NEW → ASSIGNED
Reporter

Comment 4

Last year
mozreview-review
Comment on attachment 8964696 [details]
Bug 1429179 - Add policy to clear data on shutdown.

https://reviewboard.mozilla.org/r/233398/#review239376
Attachment #8964696 - Flags: review?(felipc) → review+
We're sorry, Autoland could not rebase your commits for you automatically. Please manually rebase your commits and try again.

hg error in cmd: hg rebase -s 3c1781d850bd56cd87f8713efce4daa0995ee0e5 -d 61c57ad4f4f4: rebasing 456140:3c1781d850bd "Bug 1429179 - Add policy to clear data on shutdown. r=Felipe" (tip)
merging browser/components/enterprisepolicies/Policies.jsm
merging browser/components/enterprisepolicies/schemas/policies-schema.json
merging browser/components/enterprisepolicies/tests/browser/browser_policies_simple_pref_policies.js
warning: conflicts while merging browser/components/enterprisepolicies/tests/browser/browser_policies_simple_pref_policies.js! (edit, then use 'hg resolve --mark')
unresolved conflicts (see hg resolve, then hg rebase --continue)

Comment 6

Last year
Pushed by felipc@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/7f5c38e04808
Add policy to clear data on shutdown. r=felipe
[Tracking Requested - why for this release]:
Enterprise Policies
Comment on attachment 8964696 [details]
Bug 1429179 - Add policy to clear data on shutdown.

Approval Request Comment
[Feature/Bug causing the regression]: Enterprise Policies
[User impact if declined]: Policy to clear data on shutdown
[Is this code covered by automated tests?]: Yes
[Has the fix been verified in Nightly?]: not yet
[Needs manual test from QE? If yes, steps to reproduce]: QA will handle it
[List of other uplifts needed for the feature/fix]: none
[Is the change risky?]: no
[Why is the change risky/not risky?]: policy just sets the right prefs for it
[String changes made/needed]: no
Attachment #8964696 - Flags: approval-mozilla-beta?

Comment 9

Last year
bugherder
https://hg.mozilla.org/mozilla-central/rev/7f5c38e04808
Status: ASSIGNED → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Target Milestone: --- → Firefox 61
We tested this on the latest nightly with JSON policy format and it is verified as fixed.
This policy checks and locks "Clear history when Nightly Close" and all of the options under the [Setting] button. 

We will retest this with adm policy format when ready.

Test cases and runs are here- https://testrail.stage.mozaws.net/index.php?/plans/view/8760
Comment on attachment 8964696 [details]
Bug 1429179 - Add policy to clear data on shutdown.

enterprise policy, approved for 60.0b11
Attachment #8964696 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
We retested this on beta builds[FX60] with ADM and JSON policy formats and it is verified as fixed.

Test cases and runs are here- https://testrail.stage.mozaws.net/index.php?/plans/view/8760
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.