Closed
Bug 1872267
Opened 11 months ago
Closed 11 months ago
Setting a integer user preference via GPO with a value of 0 makes it a boolean
Categories
(Firefox :: Enterprise Policies, defect, P3)
Firefox
Enterprise Policies
Tracking
()
RESOLVED
FIXED
123 Branch
People
(Reporter: mkaply, Assigned: mkaply)
Details
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr115+
|
Details | Review |
If you set a Preference policy like this:
"print.printer_VersaLink_C505.print_paper_size_unit": {
"Value": 0,
"Status": "user"
}
It ends up as false in about:config
We should keep the 0 int value.
Assignee | ||
Updated•11 months ago
|
Assignee: nobody → mozilla
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•11 months ago
|
||
This was done on purpose in bug 1668374.
I need to find a better way.
Assignee | ||
Updated•11 months ago
|
Summary: Setting a boolean user preference via GPO makes it a boolean → Setting a integer user preference via GPO with a value of 0 makes it a boolean
Assignee | ||
Comment 2•11 months ago
|
||
I think the best thing to do here is add an optional type on Preferences.
This is such an edge case, it's not worth overrotating
Assignee | ||
Comment 3•11 months ago
|
||
Pushed by mozilla@kaply.com:
https://hg.mozilla.org/integration/autoland/rev/9d47e26b23ab
Allow setting an explicit preference type in policy. r=kcochrane
Comment 5•11 months ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 11 months ago
status-firefox123:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 123 Branch
Assignee | ||
Comment 6•10 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D197534
Updated•10 months ago
|
Attachment #9377024 -
Flags: approval-mozilla-esr115?
Comment 7•10 months ago
|
||
Uplift Approval Request
- Risk associated with taking this patch: Low
- String changes made/needed: None
- User impact if declined: Can't set certain pref policies correctly (parity with 123)
- Explanation of risk level: Policy only
- Code covered by automated testing: yes
- Is Android affected?: no
- Fix verified in Nightly: yes
- Steps to reproduce for manual QE testing: N/A
- Needs manual QE test: no
Updated•10 months ago
|
Attachment #9377024 -
Flags: approval-mozilla-esr115? → approval-mozilla-esr115+
Updated•10 months ago
|
status-firefox-esr115:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•