Các câu trả lời gần đây cho Is anyone else finding that new (as of couple days ago) Firefox isn't displaying embedded fonts correctly?https://support.mozilla.org/vi/questions/12644002019-07-15T17:41:58-07:00I have rolled back to previous version. Version 68, is a seriously botched release.
You cannot even2019-07-15T17:41:58-07:00paul.corlesshttps://support.mozilla.org/vi/questions/1264400#answer-1237815<p>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.
</p>This also breaks any one who has an external XSLT; the bug is private in the tracker database. What 2019-07-15T02:29:43-07:00aolszowkahttps://support.mozilla.org/vi/questions/1264400#answer-1237553<p>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?
</p><p>This is a pretty fundamental change and the description of the CVE really reeks of "Code Execution Results in Code Execution".
</p>This is a major problem for web developers using dreamweaver.
In preview mode the URL is going to s2019-07-11T21:43:04-07:00paul.corlesshttps://support.mozilla.org/vi/questions/1264400#answer-1236682<p>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.
</p><p>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.
</p><p>Every version of firefox previously has worked just fine.
</p>basically this change in 68 was isolating files in your local environment from each other, so a down2019-07-11T03:33:27-07:00philipphttps://support.mozilla.org/vi/questions/1264400#answer-1236489<p>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.
</p>Yes! That did the trick, many thanks.
Mind you, I still don't understand why the problem arises…
2019-07-11T03:04:58-07:00majjickhttps://support.mozilla.org/vi/questions/1264400#answer-1236485<p>Yes! That did the trick, many thanks.
</p><p>Mind you, I still don't understand why the problem arises…
</p>hi paul, this is likely happening due to this security fix: https://www.mozilla.org/en-US/security/a2019-07-11T02:40:54-07:00philipphttps://support.mozilla.org/vi/questions/1264400#answer-1236481<p>hi paul, this is likely happening due to this security fix: <a href="https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11730" rel="nofollow">https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11730</a>
</p><p>try to change <em>privacy.file_unique_origin</em> 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).
</p>