1461542 - Firefox Quantum 60.0 displays fonts as a question mark inside a square on MAC OSX El Capitan

Status: RESOLVED DUPLICATE of bug 1460917

(Core :: Security: Process Sandboxing, defect)

Description

[jbailey]

Attachment: www.ruffhaus.com.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180503143129

Steps to reproduce:

Visited various websites


Actual results:

fonts display as question mark inside a box


Expected results:

fonts should display as text

Comment 1

[Gingerbread Man]

Looks like a duplicate of bug 1460949. Please take the following steps then report the results:

1. Enter the following into the address bar:
about:config?filter=security.sandbox.content.level

2. When the warning appears, click the big button to bypass it.

3. On the next page, double-click the security.sandbox.content.level entry. In the box that pops up, type 1 then press the OK button.

4. Quit, then restart Firefox. Does the problem still occur?


I look at one of the span elements and developer tools shows the following rule applied:

font-family: "Helvetica Neue","Arial","sans-serif";

Helvetica Neue is a font bundled with Mac OS, but not Windows.

Comment 2

[jbailey]

I did the steps and it worked this time. Why is this necessary? Is my security now at risk?

Please explain your comment:
I look at one of the span elements and developer tools shows the following rule applied:

font-family: "Helvetica Neue","Arial","sans-serif";

Helvetica Neue is a font bundled with Mac OS, but not Windows.

Comment 3

[Gingerbread Man]

(In reply to jbailey from comment #2)
> I did the steps and it worked this time. Why is this necessary?
> Is my security now at risk?

Comment 1 were troubleshooting steps that determined the fonts are blocked by Firefox's sandboxing policy, meaning you have fonts installed in a non-standard location. I'm not familiar with sandboxing details, so I can't tell you the implications of browsing with that setting modified.

> Please explain your comment:

It's a note for any developers looking into this.

Comment 4

[Haik Aftandilian [:haik]]

(In reply to Gingerbread Man from comment #3)
> (In reply to jbailey from comment #2)
> > I did the steps and it worked this time. Why is this necessary?
> > Is my security now at risk?
> 
> Comment 1 were troubleshooting steps that determined the fonts are blocked
> by Firefox's sandboxing policy, meaning you have fonts installed in a
> non-standard location. I'm not familiar with sandboxing details, so I can't
> tell you the implications of browsing with that setting modified.

Setting security.sandbox.content.level to 1 reduces the strength of our content security sandbox. I consider it OK to use as a temporary workaround.

I think the problem you are hitting is bug 1460917. We're working on getting this problem fixed ASAP at which time the workaround will no longer be needed. I'm going to close this bug as a duplicate of bug 1460917. You'll continue to receive notifications as progress is made towards getting the bug fixed.