Closed Bug 1772503 Opened 2 years ago Closed 11 months ago

BUG: Conflict between DisableFirefoxStudies and UserMessaging policies

Categories

(Firefox :: Enterprise Policies, defect, P3)

Firefox 91
Desktop
All
defect

Tracking

()

VERIFIED FIXED
116 Branch
Tracking Status
firefox-esr102 --- wontfix
firefox105 --- wontfix
firefox106 --- wontfix
firefox107 --- wontfix
firefox114 --- wontfix
firefox115 --- verified
firefox116 --- verified

People

(Reporter: horwedel-heiko, Assigned: mkaply)

Details

Attachments

(3 files)

Attached image conflict.png

Steps to reproduce:

I found two bugs:

  • The policies for DisableFirefoxStudies and UserMessaging (ExtensionRecommendations, FeatureRecommendations) conflicting.

If you set the policy DisableFirefoxStudies the ui elements for the following settings are unchecked and looked:

  • Settings UI > General > Browsing > Recommend extensions as you browse
  • Settings UI > General > Browsing > Recommend features as you browse

If you the disable the policies for ExtensionRecommendations and FeatureRecommendations the ui settings aren't looked anymore. It is even possible to enable the settings regardless of the state of DisableFirefoxStudies.

Note: We configure the policies using Active Directory GPOs.
FF 91.10.0esr; ADMX v3.10

Attached image disable studies.png
Component: Untriaged → Enterprise Policies

The severity field is not set for this bug.
:mkaply, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(mozilla)
Severity: -- → S3
Flags: needinfo?(mozilla)
Priority: -- → P3

I was able to reproduce this issue on my end as well, Setting those prefs in the policies.json file will unlock the extensions and feature recommendations.

Status: UNCONFIRMED → NEW
Has STR: --- → yes
Ever confirmed: true
OS: Unspecified → All
Hardware: Unspecified → Desktop

I think there is only one issue here, the conflict between DisableFirefoxStudies and UserMessaging (ExtensionRecommendations, FeatureRecommendations) are causing the Extension and Feature Recommendations to uncheck and unlock. I will mark Bug 1772504 as a duplicate for this issue since that the same thing is causing it, but please feel free to reopen that one if these are indeed 2 separate issues.

No longer duplicate of this bug: 1772504

For this bug, what I'm going to do is add code to our policy code that if something is already locked, another policy can't unlock it.

Assignee: nobody → mozilla
Status: NEW → ASSIGNED
Pushed by mozilla@kaply.com:
https://hg.mozilla.org/integration/autoland/rev/208ba0efbefb
Keep policy locked preferences locked. r=mhowell

Didn't realize there was a test for this elsewhere. Fix ready, running on try to see if there is anything else.

Flags: needinfo?(mozilla)
Pushed by mozilla@kaply.com:
https://hg.mozilla.org/integration/autoland/rev/81ee49e2175e
Keep policy locked preferences locked. r=mhowell,necko-reviewers,kershaw
Status: ASSIGNED → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch

This issue is verified as fixed in our latest build 116.0a1 (2023-06-21). Updating the remaining flags.

The patch landed in nightly and beta is affected.
:mkaply, is this bug important enough to require an uplift?

  • If yes, please nominate the patch for beta approval.
  • If no, please set status-firefox115 to wontfix.

For more information, please visit BugBot documentation.

Flags: needinfo?(mozilla)

Comment on attachment 9339309 [details]
Bug 1772503 - Keep policy locked preferences locked. r?mhowell

Beta/Release Uplift Approval Request

  • User impact if declined: Some policies can stomp on each other.
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: Yes
  • 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): Policy only, automated test, tested by QA

Main reason I want this is it will make ESR 115 merges easier.

  • String changes made/needed:
  • Is Android affected?: No
Flags: needinfo?(mozilla)
Attachment #9339309 - Flags: approval-mozilla-beta?

Comment on attachment 9339309 [details]
Bug 1772503 - Keep policy locked preferences locked. r?mhowell

Approved for 115.0 RC1.

Attachment #9339309 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

This issue is verified as fixed in our latest Beta 115.0b10

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: