X
Tap here to go to the mobile version of the site.

ஆதரவு மன்றம்

Is anyone else finding that new (as of couple days ago) Firefox isn't displaying embedded fonts correctly?

  • 6 replies
  • 4 இந்த பிரச்னைகள் உள்ளது
  • Last reply by paul.corless
பதிவிடப்பட்டது

I have an embedded font on my website that I use for the header, and it displays fine. I have a development copy of the website on my hard disk, and that displayed fine too until Firefox 68.0; but now it uses the second font in my list, instead of the first.

So: some bug in the code of the copy on my disk, I thought. But when I open it in Safari, Chrome or Brave, it displays correctly.

The W3C CSS validation service finds no error in the code.

I'm stumped. Any ideas?

I have an embedded font on my website that I use for the header, and it displays fine. I have a development copy of the website on my hard disk, and that displayed fine too until Firefox 68.0; but now it uses the second font in my list, instead of the first. So: some bug in the code of the copy on my disk, I thought. But when I open it in Safari, Chrome or Brave, it displays correctly. The W3C CSS validation service finds no error in the code. I'm stumped. Any ideas?

தீர்வு தேர்ந்தெடுக்கப்பட்டது

hi paul, this is likely happening due to this security fix: https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11730

try to change privacy.file_unique_origin to false in about:config, restart firefox and see if this can make a difference (please note that this makes you vulnerable to the described security problem though).

Read this answer in context 2
மேற்கோள்

Additional System Details

நிறுவப்பட்ட நிரல்கள்

  • Shockwave Flash 32.0 r0
  • Shockwave Flash 10.0 r45

பயன்பாடு

  • User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Firefox/68.0

கூடுதல் தகவல்

philipp
  • Top 25 Contributor
  • Moderator
5291 தீர்வுகள் 23375 பதில்கள்
பதிவிடப்பட்டது

தீர்வு தேர்ந்தெடுக்கப்பட்டது

hi paul, this is likely happening due to this security fix: https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11730

try to change privacy.file_unique_origin to false in about:config, restart firefox and see if this can make a difference (please note that this makes you vulnerable to the described security problem though).

hi paul, this is likely happening due to this security fix: https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11730 try to change ''privacy.file_unique_origin'' to false in about:config, restart firefox and see if this can make a difference (please note that this makes you vulnerable to the described security problem though).
இது உங்களுக்கு பயனுள்ளதாக இருந்ததா? 2
மேற்கோள்
பதிவிடப்பட்டது

கேள்வியின் உரிமையாளர்

Yes! That did the trick, many thanks.

Mind you, I still don't understand why the problem arises…

Yes! That did the trick, many thanks. Mind you, I still don't understand why the problem arises…
இது உங்களுக்கு பயனுள்ளதாக இருந்ததா?
மேற்கோள்
philipp
  • Top 25 Contributor
  • Moderator
5291 தீர்வுகள் 23375 பதில்கள்
பதிவிடப்பட்டது

உதவிகரமான பதில்

basically this change in 68 was isolating files in your local environment from each other, so a downloaded malicious html file wouldn't be able to access other content on your disk once opened.

basically this change in 68 was isolating files in your local environment from each other, so a downloaded malicious html file wouldn't be able to access other content on your disk once opened.
இது உங்களுக்கு பயனுள்ளதாக இருந்ததா? 2
மேற்கோள்
paul.corless 0 தீர்வுகள் 2 பதில்கள்
பதிவிடப்பட்டது

This is a major problem for web developers using dreamweaver. In preview mode the URL is going to start with file:/// Which is then going to block all fonts because of your CORS policy.

This now means none of my fonts, webfonts, icon fonts now show in firefox browser without the above hack. This is a serious problem for web designers.

Every version of firefox previously has worked just fine.

This is a major problem for web developers using dreamweaver. In preview mode the URL is going to start with file:/// Which is then going to block all fonts because of your CORS policy. This now means none of my fonts, webfonts, icon fonts now show in firefox browser without the above hack. This is a serious problem for web designers. Every version of firefox previously has worked just fine.

paul.corless மூலமாக திருத்தப்பட்டது

இது உங்களுக்கு பயனுள்ளதாக இருந்ததா?
மேற்கோள்
aolszowka 0 தீர்வுகள் 1 பதில்கள்
பதிவிடப்பட்டது

This also breaks any one who has an external XSLT; the bug is private in the tracker database. What is the acceptable work around to get this to work?

This is a pretty fundamental change and the description of the CVE really reeks of "Code Execution Results in Code Execution".

This also breaks any one who has an external XSLT; the bug is private in the tracker database. What is the acceptable work around to get this to work? This is a pretty fundamental change and the description of the CVE really reeks of "Code Execution Results in Code Execution".
இது உங்களுக்கு பயனுள்ளதாக இருந்ததா?
மேற்கோள்
paul.corless 0 தீர்வுகள் 2 பதில்கள்
பதிவிடப்பட்டது

I have rolled back to previous version. Version 68, is a seriously botched release. You cannot even get out of responsive mobile view in developer tools. As the toggle mobile/desktop no longer even works.

I have rolled back to previous version. Version 68, is a seriously botched release. You cannot even get out of responsive mobile view in developer tools. As the toggle mobile/desktop no longer even works.
இது உங்களுக்கு பயனுள்ளதாக இருந்ததா?
மேற்கோள்
கேள்வி எழுப்பு

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.