Cannot force using selected fonts since 118 release
Categories
(Core :: Privacy: Anti-Tracking, defect)
Tracking
()
People
(Reporter: chmielcode, Unassigned)
References
(Blocks 1 open bug)
Details
Steps to reproduce:
Refresh firefox, pick new default fonts and uncheck "allow websites to use other fonts" (I'm translating from my language).
First the fonts are enforced as before, but then after adjusting other settings (e.g. I've set protection mode to custom for test) this option does not work anymore.
Actual results:
No way to prevent websites from using their fonts.
Expected results:
As it used to be before version 118, all text should be displayed with my custom fonts and no other.
|
||
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Privacy: Anti-Tracking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
Reporter | |
Comment 2•1 year ago
|
||
Please also consider restarting firefox after changing settings if the bug does not get triggered by that alone. For now I've moved to ESR and the problem is gone.
|
||
Comment 3•1 year ago
|
||
This is probably of the new Fingerprinting Protection feature we have rolled out to prevent websites from fingerprinting you based on locally installed fonts.
This feature is, by default, enabled in PBM windows. It is also enabled everywhere if ETP Strict is enabled. And it can be enabled individually in ETP Custom (under the label 'Suspected Fingerprinters'.
To regain the ability to use your custom font, you will need to change this ETP Setting. (There are other, more complicated and granular preferences that can control its behavior, but we don't generally recommend setting those unless you're comfortable tweaking things in about:config and keeping them up to date as we change the feature.)
I would recommend doing that to see if it fixes your issue - if it does (or doesn't) - please let us known. Then you can decide if you would prefer to be more fingerprintable to online trackers in order to use your custom font. (Perhaps you can accept the tracking in normal windows where you may be already logged into services; but you'd like to keep the protection in PBM.)
|
|
Reporter | |
Comment 4•1 year ago
|
||
(In reply to Tom Ritter [:tjr] from comment #3)
This is probably of the new Fingerprinting Protection feature we have rolled out to prevent websites from fingerprinting you based on locally installed fonts.
This feature is, by default, enabled in PBM windows. It is also enabled everywhere if ETP Strict is enabled. And it can be enabled individually in ETP Custom (under the label 'Suspected Fingerprinters'.
To regain the ability to use your custom font, you will need to change this ETP Setting. (There are other, more complicated and granular preferences that can control its behavior, but we don't generally recommend setting those unless you're comfortable tweaking things in about:config and keeping them up to date as we change the feature.)
I would recommend doing that to see if it fixes your issue - if it does (or doesn't) - please let us known. Then you can decide if you would prefer to be more fingerprintable to online trackers in order to use your custom font. (Perhaps you can accept the tracking in normal windows where you may be already logged into services; but you'd like to keep the protection in PBM.)
Thank you! Unchecking "Suspected fingerprinters" fixes the issue. Could it be possible to add a warning like "switching this on will disable custom font setting that you have right now"? For me, at least, the perfect solution would be to keep the "Suspected fingerprinters" on and control the part that disables font enforcing: "[] allow custom fonts - you will be more fingerprintable". This or maybe it is possible to still use my fonts and just inform websites about using the defaults?
|
||
Comment 5•1 year ago
|
||
The fix for bug 1850672 is now requesting uplift approval to the release version.
|
|
||
Comment 6•1 year ago
|
||
I don't believe this is a dupe of that bug; however it is working as intended. We're in the process of improving the support page to explain the consequences of this setting.
Description
•