BUG: Conflict between DisableFirefoxStudies and UserMessaging policies
Categories
(Firefox :: Enterprise Policies, defect, P3)
Tracking
()
People
(Reporter: horwedel-heiko, Assigned: mkaply)
Details
Attachments
(3 files)
293.10 KB,
image/png
|
Details | |
305.40 KB,
image/png
|
Details | |
48 bytes,
text/x-phabricator-request
|
dmeehan
:
approval-mozilla-beta+
|
Details | Review |
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
Github-Issue: https://github.com/mozilla/policy-templates/issues/914
Comment 3•2 years ago
|
||
The severity field is not set for this bug.
:mkaply, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Comment 4•2 years ago
|
||
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.
Comment 5•2 years ago
|
||
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.
Assignee | ||
Comment 7•11 months ago
|
||
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 | ||
Comment 8•11 months ago
|
||
Updated•11 months ago
|
Pushed by mozilla@kaply.com: https://hg.mozilla.org/integration/autoland/rev/208ba0efbefb Keep policy locked preferences locked. r=mhowell
Comment 10•11 months ago
|
||
Backed out for causing xpc failures in netwerk/test/unit/test_trr_enterprise_policy.js
Backout link: https://hg.mozilla.org/integration/autoland/rev/272d7188fe71c94facdcd15027c7b5385863315f
Assignee | ||
Comment 11•11 months ago
|
||
Didn't realize there was a test for this elsewhere. Fix ready, running on try to see if there is anything else.
Comment 12•11 months ago
|
||
Pushed by mozilla@kaply.com: https://hg.mozilla.org/integration/autoland/rev/81ee49e2175e Keep policy locked preferences locked. r=mhowell,necko-reviewers,kershaw
Comment 13•11 months ago
|
||
bugherder |
Comment 14•11 months ago
|
||
This issue is verified as fixed in our latest build 116.0a1 (2023-06-21). Updating the remaining flags.
Comment 15•11 months ago
|
||
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
towontfix
.
For more information, please visit BugBot documentation.
Assignee | ||
Comment 16•11 months ago
|
||
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
Comment 17•11 months ago
|
||
Comment on attachment 9339309 [details]
Bug 1772503 - Keep policy locked preferences locked. r?mhowell
Approved for 115.0 RC1.
Comment 18•11 months ago
|
||
bugherder uplift |
Updated•11 months ago
|
Comment 19•11 months ago
|
||
This issue is verified as fixed in our latest Beta 115.0b10
Description
•