Closed Bug 1573932 Opened 4 years ago Closed 4 years ago

Enterprise policy should be able to opt-out of extended triplets

Categories

(Firefox :: Messaging System, enhancement)

Product:
Firefox
Component:
Messaging System
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
Firefox 70
Tracking Flags:
Tracking Status
firefox69 --- fixed
firefox70 --- fixed

People

(Reporter: k88hudson, Assigned: mkaply)

References

Details

Attachments

(1 file)

Bug 1573932 - Disable extended triplets for certain policies.
47 bytes, text/x-phabricator-request
RyanVM
: approval-mozilla-beta+
Details | Review

We should give Enterprise builds the option to opt-out of extended triplets via a pref if possible, since they are also able to opt-out of about:welcome.

This could be accomplished with modifying the asrouter.onboarding pref but it might be preferable to use a separate pref.

Summary: We should give Enterprise policy the option to opt-out of extended triplets → Enterprise policy should be able to opt-out of extended triplets

Enterprise has an OverrideFirstRunPage which I guess we can check if startup.homepage_welcome_url is set to "about:welcome"

https://searchfox.org/mozilla-central/rev/428cf94f4ddfb80eebc6028023a7d89eb277791b/browser/components/enterprisepolicies/Policies.jsm#972-975

If we're ok with also disabling the triplets on about:welcome, we could accomplish this if the policy set trailhead.firstrun.branches pref to control (or just join if we wanted to enable the modal)

So I'm wondering when to set this pref in policy.

I'm thinking if either FirefoxHome is customized (at all) or first run page is overridden, I should set this pref.

What's control versus join?

Both "control" and "join" have about:welcome dialogs for FxA signups (with different messaging; and no triplets). Setting trailhead.firstrun.branches to "nofirstrun" will show no interrupt nor triplets on about:welcome as well as no triplets on about:newtab/home.

Assignee: nobody → mozilla
Status: NEW → ASSIGNED

I went with three policies that can disable them

  1. if sync is turned off.
  2. If they've modified the new tab page (FirefoxHome) in any way.
  3. If they've changed the welcome page.

I did not add an explicit new policy.

Pushed by mozilla@kaply.com:
https://hg.mozilla.org/integration/autoland/rev/bef138f4cafb
Disable extended triplets for certain policies. r=Mardak

https://hg.mozilla.org/mozilla-central/rev/bef138f4cafb

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox70: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 70

Comment on attachment 9087452 [details]
Bug 1573932 - Disable extended triplets for certain policies.

Beta/Release Uplift Approval Request

  • User impact if declined: Triplets appear in enterprises. Needed for Skyline.
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Nightly?: No
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): Just sets an additional preference with a couple policies.
  • String changes made/needed:
Attachment #9087452 - Flags: approval-mozilla-beta?

Comment on attachment 9087452 [details]
Bug 1573932 - Disable extended triplets for certain policies.

Allow enterprise policies to be set to opt out of new relationship scoping work shipping in 69. Approved for 69.0rc1.

Attachment #9087452 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
You need to log in before you can comment on or make changes to this bug.