X
點擊此處開啟此網站的行動版。

技術支援討論區

No display of local fonts on my PC (not a server) where to change it Firefox 68 - win10

已張貼

After update to Firefox 68 on my pc Firefox can't display my local fonts. Fonts folder is in same folder as index.html css folder. Images Chrome to the right Firefox to the Left. No of the solution works for me, I cant find of the file/index on my computer. Best Regards Bjorn Danebod

After update to Firefox 68 on my pc Firefox can't display my local fonts. Fonts folder is in same folder as index.html css folder. Images Chrome to the right Firefox to the Left. No of the solution works for me, I cant find of the file/index on my computer. Best Regards Bjorn Danebod
附加的畫面擷圖

被選擇的解決方法

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

You can type 'unique' (without quotes) in its search bar at the top.

從原來的回覆中察看解決方案 1
引用

額外的系統細節

已安裝的外掛程式

  • Shockwave Flash 32.0 r0

應用程式

  • User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

更多資訊

philipp
  • Top 25 Contributor
  • Moderator
5281 個解決方法 23332 個答案

hi, this is fallout from the following privacy/security fix in firefox 68: https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11730

in an upcoming version, mozilla is planning to loosen that restriction for fonts again, since that has been a frequent piece of feedback in the last couple of days: https://bugzilla.mozilla.org/show_bug.cgi?id=1565942

in the meantime it's possible to revert to the old behaviour by toggling the privacy.file_unique_origin preference in about:config to false and restarting firefox once (please note that this makes you vulnerable to the described security problem though).

hi, this is fallout from the following privacy/security fix in firefox 68: https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11730 in an upcoming version, mozilla is planning to loosen that restriction for fonts again, since that has been a frequent piece of feedback in the last couple of days: https://bugzilla.mozilla.org/show_bug.cgi?id=1565942 in the meantime it's possible to revert to the old behaviour by toggling the ''privacy.file_unique_origin'' preference in about:config to false and restarting firefox once (please note that this makes you vulnerable to the described security problem though).
這篇文章有幫助嗎?
引用

提出問題者

Where to find this: privacy.file_unique_origin or about:config???

Where to find this: privacy.file_unique_origin or about:config???
這篇文章有幫助嗎?
引用
cor-el
  • Top 10 Contributor
  • Moderator
17344 個解決方法 156782 個答案

選擇的解決方法

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

You can type 'unique' (without quotes) in its search bar at the top.

You can open the <b>about:config</b> page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue. *https://support.mozilla.org/en-US/kb/about-config-editor-firefox You can type 'unique' (without quotes) in its search bar at the top.

由 cor-el 於 修改

這篇文章有幫助嗎? 1
引用
問個問題

如果您還沒有帳號,您必須先 登入您的帳號 來回覆文章。請 開始一個新問題