1608240 - Provide a policy for disabling CFR and whatsnew

Status: VERIFIED FIXED

(Firefox :: Enterprise Policies, enhancement, P1)

Description

[Mike Kaply [:mkaply]]

We need a policy that affects these three prefs:

browser.messaging-system.whatsNewPanel.enabled
browser.newtabpage.activity-stream.asrouter.userprefs.cfr.features
browser.newtabpage.activity-stream.asrouter.userprefs.cfr.addons

I think we should use one policy for all that just turns off all these messaging (I don't think we need individual flags - I doubt folks would want one but not the other.

I could be wrong.

Opinions welcome.

Comment 1

[Mike Kaply [:mkaply]]

Attachment: Bug 1608240 - Add a policy to control user messaging. r?mconley

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/0f5ceff56bba
Add a policy to control user messaging. r=mconley,fluent-reviewers,flod

Comment 3

[Razvan Maries]

https://hg.mozilla.org/mozilla-central/rev/0f5ceff56bba

Comment 4

[Mike Kaply [:mkaply]]

Attachment: Patch for ESR

This is an ESR specific patch. It removes WhatsNew and adds the changes frmo bug 1622045

[Approval Request Comment]
If this is not a sec:{high,crit} bug, please state case for ESR consideration: Policy change for parity with Firefox 75.
User impact if declined: No policy for UserMessaging
Fix Landed on Version: 75
Risk to taking this patch (and alternatives if risky): Low

See https://wiki.mozilla.org/Release_Management/ESR_Landing_Process for more info.

This does involve a new string. We have prior approval to not worry about translation for policies.

Comment 5

[Emil Ghitta, QA [:emilghitta]]

This is verified fixed using Firefox 75.0b5 (BuildId:20200317211402) on Windows 10 64bit, macOS 10.14 and Ubuntu 18.04 64bit.

The prefs in question can be successfully disabled/manipulated via the policy implementation.

Verified the following:

• Verified that they are successfully disabled and locked in about:config.
• The WhatsNewPanel is no longer displayed for the user (if disabled by the policy).
• CFR notifications for addons & features are no longer displayed for the user (if disabled by the policy).
• Both "Recommend extensions as you browse" & "Recommend features as you browse" in about:preferences#general are automatically checked/unchecked & locked (depending on the policy setup).

Leaving the qe-verify+ flag and a ni? on myself as a reminder to verify this in esr once it lands.

Comment 6

[Ryan VanderMeulen [:RyanVM]]

Comment on attachment 9134181 [details] [diff] [review]
Patch for ESR

Policy engine update needed for release parity. Approved for 68.7esr.

Comment 7

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/releases/mozilla-esr68/rev/b311f13f52a0

Comment 8

[Emil Ghitta, QA [:emilghitta]]

This is verified fixed using Firefox 68.7.0esr (provided in comment 7) on Windows 10 64bit, macOS 10.14 and Ubuntu 18.04 64bit.