EnableTrackingProtection policy doesn't allow to block user specified exceptions or set the cookie dropdown value
Categories
(Firefox :: Enterprise Policies, enhancement)
Tracking
()
People
(Reporter: pascal.reintjens, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0
Steps to reproduce:
- Created a policies.json file with the following contents:
{
"policies": {
"EnableTrackingProtection": {
"Value": true,
"Locked": true,
"Cryptomining": true,
"Fingerprinting": true,
"EmailTracking": true,
"Exceptions": ["https://test.de"]
}
}
}
- Subsequently, placed this file within the installation directory: C:\Program Files\Mozilla Firefox\distribution\policies.json
- restarted the browser and went to
Settings > Privacy & Security > Enhanced Tracking Protection
Actual results:
The policy doesn't allow to specify the value of the cookie dropdown option, which means that the user still needs to choose / can choose the value.
The policy doesn't allow to lock the Exceptions, therefore the user can click the "Manage exceptions..." button and add his own exceptions. Secondly when the user is on a page, he can click the shield icon and add pages via the "Enhanced Tracking Protection" toggle as well. Additionally it is not possible to change the radio button in the settings to strict via EnableTrackingProtection.
Expected results:
Both the cookie dropdown option and the option to lock the exceptions should be possible to be set via EnableTrackingProtection.
Locking the exceptions should result in the state, that the user can't add exceptions via "Manage exceptions..." Button in the settings. Additionally the user then should be unable when he is on a page, to change the "enhanced tracking protection" toggle on the shield icon.
Additionally it should be possible to set the radio button for the enhanced tracking protection in the settings to strict via EnableTrackingProtection.
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Enterprise Policies' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
| Reporter | ||
Comment 2•2 years ago
|
||
I'm closing this bug, since i overlooked an setting and opening a new bug with the still applicable description.
Description
•