Closed
Bug 1407294
Opened 7 years ago
Closed 7 years ago
Typography visualisation issue
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1404919
People
(Reporter: adressespamdemerde, Unassigned, NeedInfo)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20171002220106
Steps to reproduce:
Upload the last Firefox version
Actual results:
Typo on some websites, and sometime only on some parts of websites are corrupted so that we can read nothing
Expected results:
Have a correct visualization
Comment 1•7 years ago
|
||
Could you provide the address of a page where you are seeing this bug please?
Flags: needinfo?(adressespamdemerde)
Updated•7 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Comment 3•7 years ago
|
||
adressespamdemerde@gmx.fr,
Are you using a font manager application such as Right Font or Linotype FontExplorer?
Could you run the following command in Terminal (/Applications/Utilities/Terminal) and then attach the resulting fontdata.txt file?
$ system_profiler SPFontsDataType > fontdata.txt
The collected fontdata.txt file will include paths from your system and which fonts you have installed. If you would prefer not to post that, you could email it to me.
Thanks!
Reporter | ||
Comment 4•7 years ago
|
||
Hi guys, it's still not working proprelly and I keep on finding websites with the same problem. In the meantime the old versions of Firefox, such as the 54 has been made unvailable. Maybe if the temporary solution is to reinstall an old version (that used to work fine) ?
Flags: needinfo?(adressespamdemerde)
Comment 5•7 years ago
|
||
As a workaround, if you open about:config and change the setting of security.sandbox.content.level to 1 (instead of 3), that should workaround the problem. But it won't help us figure out why you're seeing this problem. If you could collect the output of "system_profiler SPFontsDataType" and attach it here, that would help us understand what about your font setup causes the problem and help us get it fixed. Could you collect the output from the command "system_profiler SPFontsDataType"? Thanks!
Flags: needinfo?(adressespamdemerde)
Reporter | ||
Comment 6•7 years ago
|
||
Here is the bug file as requested by Haik. Thanks for your help guys
Flags: needinfo?(adressespamdemerde)
Comment 7•7 years ago
|
||
(In reply to adressespamdemerde@gmx.fr from comment #6)
> Created attachment 8917615 [details]
> Bug file.rtf
>
> Here is the bug file as requested by Haik. Thanks for your help guys
Thanks, that helps us understand what's going on. From the attachment, I can see some fonts on your system that are going to be blocked by our sandbox in build 56. We're working on getting this fixed.
Specifically, Extensis "Suitcase Fusion" is being used to manage fonts and that (by default) places fonts in the following directory. Many of those 300 fonts don't have filename extensions. (Suitcase Fusion appears to store fonts in a special directory/indexed layout including renaming of fonts to filenames that don't have extensions.)
~/Library/Extensis/Suitcase Fusion/Suitcase Fusion.fontvault/
Additionally, there are two postscript fonts in /System/Library/Fonts/ without filename extensions: Times LT MM, and Helvetica LT MM.
Reporter | ||
Comment 8•7 years ago
|
||
I found the fonts in my library and add them an extension .ttf
After restarting Firefox the problem is the same. So I tried .ttc and it's the same. How long do you think it's gonna take to solve this ? Would it need to download another version ? Thanks
Comment 9•7 years ago
|
||
Did you try Haik's suggestion from comment 5?
"open about:config and change the setting of security.sandbox.content.level to 1 (instead of 3)"
(and then restart Firefox). As far as I know, that should avoid the problem.
Comment 10•7 years ago
|
||
I've posted a build of Firefox with a fix for this problem on https://bugzilla.mozilla.org/show_bug.cgi?id=1404919#c21
If you could give that a try and let us know if it works for you, we'd really appreciate it. See bug 1404919 for more information. You'll need to revert security.sandbox.content.level to 3 to properly test the fix.
Flags: needinfo?(adressespamdemerde)
You need to log in
before you can comment on or make changes to this bug.
Description
•