1771955 - "Allow Firefox to send backlogged crash reports on your behalf" preference doesn't look disabled when locked

Status: VERIFIED FIXED

(Firefox :: Settings UI, defect, P3)

Description

[Mike Kaply [:mkaply]]

If you lock:

browser.crashReports.unsubmittedCheck.autoSubmit2

using policy, the preferences UI isn't locked.

Comment 1

[Pascal Reintjens]

In part this is still the case today with the lastest ESR (115.9.1).

Here is a testcase:

1. Created a policies.json file with the following contents:

{
	"policies": {		
		"Preferences": {
			"browser.crashReports.unsubmittedCheck.autoSubmit2": {
				"Value": false,
				"Status": "locked"
			}
		},
		"DisableTelemetry": true
	}	
}

2. Subsequently, placed this file within the installation directory: C:\Program Files\Mozilla Firefox\distribution\policies.json
3. restarted the browser and went to Settings > Privacy & Security > Firefox Data Collection and Use

=> When setting this policy, the option Allow Firefox to send backlogged crash reports on your behalf is disabled, so the user can't enable the corresponding checkbox by clicking on it, but the text of the option doesn't get greyed out so, for the user it looks like he could activate it.

For comparison, the DisableTelemetry option results in graying out Allow Firefox to send technical and interaction data to Mozilla and Allow Firefox to make personalized extension recommendations like any other setting which gets disabled and locked.

Comment 2

[:Gijs (he/him)]

Attachment: Bug 1771955 - fix HTML label associations to look disabled when the pref is locked, r?mkaply!,#settings-reviewers

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/0e4693cecc61
fix HTML label associations to look disabled when the pref is locked, r=mkaply,settings-reviewers,desktop-theme-reviewers,dao,mossop

Comment 4

[Sandor Molnar[:smolnar]]

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

Comment 5

[Catalin Sasca, Desktop Test Engineering [:csasca]]

Reproduced the issue on Firefox 103.0a1 on macOS 14.5 by following the infos provided in Comment 0.

The issue is fixed on Firefox 127.0b2. Tests were performed on macOS 14.5, Windows 11 and Ubuntu 24.04.