ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

How to get rid of "Request for font YOUR_FONT_NAME_HERE blocked at visibility level 2 (requires 3)" warning and get your font working?

  • 3 ردود
  • 1 has this problem
  • 104 views
  • آخر ردّ كتبه antizilla

more options

I updated from version 106 to the latest version just now and my user-defined fonts stopped displaying on a local HTML page (stored locally on my computer); this warning showing up in the console: "Request for font FONT_NAME_HERE blocked at visibility level 2 (requires 3)."

I specify fonts using "font-family" property (CSS).

Help me out here, please. How can I fix this (so my pages look proper again)?

Thank you.

I updated from version 106 to the latest version just now and my user-defined fonts stopped displaying on a local HTML page (stored locally on my computer); this warning showing up in the console: "Request for font FONT_NAME_HERE blocked at visibility level 2 (requires 3)." I specify fonts using "font-family" property (CSS). Help me out here, please. How can I fix this (so my pages look proper again)? Thank you.

الحل المُختار

Fingerprinting protection has been added to Strict Tracking Protection which uses a hard-coded list of visible fonts. You can switch to Custom mode and disable "Suspected fingerprinters" if fonts are more of a priority.

Read this answer in context 👍 0

All Replies (3)

more options

This is due bug 1736005, bug 1715501 and bug 1715537.

Do you have fingerprint protection enabled in Settings (or using it in a private window)?

Modified by TyDraniu

more options

الحل المُختار

Fingerprinting protection has been added to Strict Tracking Protection which uses a hard-coded list of visible fonts. You can switch to Custom mode and disable "Suspected fingerprinters" if fonts are more of a priority.

more options

TyDraniu, zeroknight, hey there and thank you for your replies.

I went to Settings, unchecked the "Suspected fingerprinters" box and the problem went away.

Thank you!