Open
Bug 1494668
Opened 7 years ago
Updated 3 years ago
Restore Defaults is not fully functional for all the Content Blocking settings
Categories
(Firefox :: Settings UI, defect, P3)
Firefox
Settings UI
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox62 | --- | unaffected |
| firefox63 | --- | affected |
| firefox64 | --- | affected |
People
(Reporter: JuliaC, Unassigned)
Details
(Whiteboard: [privacy-panel-65])
[Affected versions]:
- 64.0a1 (2018-09-27)
- 63.0b9 build1 (20180924202103)
[Affected platforms]:
- Windows 10 x64
- Ubuntu 16.04 x64
- macOS 10.13
[Steps to reproduce]:
1. Launch Firefox
2. Go to about:preferences#privacy
3. Modify the default Content Blocking settings
4. Click the "Restore Defaults" button from the top right corner of the section
[Expected result]:
- All the modified settings are successfully restored to their defaults values
[Actual result]:
- the "Send websites a Do Not Track signal that you don't want to be tracked" option is not restored
[Regression range]:
- I will provide more details as soon as possible
Comment 1•7 years ago
|
||
So this wasn't added on purpose in bug 1476217 but I don't remember whether that was an oversight/misunderstanding or actually intended. I'll mark it up for triage.
Whiteboard: [privacy-panel-64][triage]
| Reporter | ||
Comment 2•7 years ago
|
||
I forgot to mention this, as a precondition: Content Blocking must be enabled (set browser.contentblocking.ui.enabled to true and restart the browser) if isn't already.
Whiteboard: [privacy-panel-64][triage]
Comment 3•7 years ago
|
||
This wasn't an oversight on my part. There was nothing in the UX spec that stated the behavior of this button is supposed to change.
Comment 4•7 years ago
|
||
Bryan, do you want the reset button to reset the DNT settings? Either way, this is a followup.
Flags: needinfo?(bbell)
Whiteboard: [privacy-panel-65]
Updated•7 years ago
|
Priority: -- → P3
| Reporter | ||
Updated•7 years ago
|
QA Contact: jaws
Updated•7 years ago
|
QA Contact: jaws
Comment 5•3 years ago
|
||
Clear a needinfo that is pending on an inactive user.
Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.
For more information, please visit auto_nag documentation.
Flags: needinfo?(bbell)
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•