Closed
Bug 1851474
Opened 9 months ago
Closed 9 months ago
Suspected Fingerprinter settings fail to auto-synchronize across multiple open windows when modified
Categories
(Core :: Privacy: Anti-Tracking, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox-esr115 | --- | unaffected |
firefox117 | --- | unaffected |
firefox118 | --- | affected |
firefox119 | --- | affected |
People
(Reporter: sbadau, Unassigned)
References
Details
Attachments
(1 file)
4.22 MB,
video/quicktime
|
Details |
Found in
- Firefox 118
Affected versions
- Firefox 118.0b4
- Nightly 119.0a1
Tested platforms
- Affected platforms: macOS 11.7, Ubuntu 20.04 and Windows 10
Steps to reproduce
- In a normal window - open about:preferences#privacy
- Open a new private window and open about:prefecences#privacy
- In the normal window, either uncheck the "Suspected fingerprinters" option or change the dropdown to "In all windows".
Expected result
- The modification made in step 3 in the normal window should immediately reflect in the private window on the about:preferences#privacy page.
Actual result
- The change made to the "Suspected fingerprinters" setting in the first window does not appear in the second window unless the page is refreshed (F5 is pressed).
Regression range
Not a regression, it was implemented like this in Bug 1841097.
Additional notes
If a similar change is made to the "Tracking content" setting, the change is immediately visible on both about:preferences#privacy pages.
Comment 1•9 months ago
|
||
:sbadau, if you think that's a regression, could you try to find a regression range using for example mozregression?
Comment 2•9 months ago
|
||
This issue will get fixed with Bug 1841104
Reporter | ||
Comment 3•9 months ago
|
||
This issue is no longer reproducing on the latest Nightly 119.a1 - verified on macOS 11.7, Ubuntu 20.04, and Windows 10.
Comment 4•9 months ago
|
||
Close this bug per comment 3
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•