The fingerprinting protection state cleaner shouldn't clear the global zoom
Categories
(Toolkit :: Data Sanitization, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | fixed |
| firefox144 | --- | wontfix |
| firefox145 | --- | wontfix |
| firefox146 | --- | fixed |
People
(Reporter: pierov, Assigned: pierov)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr140+
|
Details | Review |
When clearing the fingerprinting state, the default zoom is also cleared: https://searchfox.org/firefox-main/rev/cb52781342cc905eda923d009fc0b678f3a8c8c6/toolkit/components/cleardata/ClearDataService.sys.mjs#458-468
While zoom can be used for linkability, we think that this is an accessibility setting that shouldn't be cleared in this way.
Comment 1•2 months ago
|
||
I agree, that seems unexpected.
Updated•2 months ago
|
Comment 2•2 months ago
|
||
Set release status flags based on info from the regressing bug 1975753
:fkilic, since you are the author of the regressor, bug 1975753, could you take a look?
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 3•2 months ago
|
||
Clearing the NI for Fatih, as we already reached the consensus to remove this.
I'll try to do it later today.
Updated•2 months ago
|
| Assignee | ||
Comment 4•2 months ago
|
||
Comment 6•2 months ago
|
||
Setting as S2 due to accessibility severity
Updated•2 months ago
|
Comment 8•2 months ago
|
||
Backed out for causing failures at browser_bug1975753_site_specific_zoom_level.js.
Backout link: https://hg-edge.mozilla.org/integration/autoland/rev/41d7609a1566094d930ee9072dde6ec098876d69
Failure log: https://treeherder.mozilla.org/logviewer?job_id=534628121&repo=autoland&task=Am7MBC6BSwqm5-TX8cq8eg.0&lineNumber=3083
| Assignee | ||
Comment 9•2 months ago
|
||
Oh! It seems setGlobal is async, but it can take an optional callback parameter.
Let me add that to promisify the change of global zoom.
Comment 10•2 months ago
|
||
Comment 11•2 months ago
|
||
| bugherder | ||
Comment 12•2 months ago
|
||
The patch landed in nightly and beta is affected.
:pierov, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox145towontfix.
For more information, please visit BugBot documentation.
Updated•2 months ago
|
Updated•2 months ago
|
Comment 13•1 month ago
|
||
Is this something we should uplift to ESR140?
| Assignee | ||
Comment 14•1 month ago
|
||
Yes please, let me create an uplift request.
Comment 15•1 month ago
|
||
firefox-esr140 Uplift Approval Request
- User impact if declined: This patch fixes another patch that was uplifted and contains code which might unexpectedly reset an accessibility option. It will be useful to Tor Browser.
- Code covered by automated testing: yes
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: -
- Risk associated with taking this patch: low
- Explanation of risk level: Unsupported configuration (RFP/FFP)
- String changes made/needed: No
- Is Android affected?: no
| Assignee | ||
Comment 16•1 month ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D271446
| Assignee | ||
Comment 18•1 month ago
|
||
No, it seems the Bug was created before the initial attempt was landed.
There's another bug to prevent potential TV failures (Bug 1999527), but as a matter of fact we've never hit those, so I don't think that needs to be uplifted either.
Updated•1 month ago
|
Updated•1 month ago
|
Comment 19•1 month ago
|
||
| uplift | ||
Description
•