Closed
Bug 949149
Opened 12 years ago
Closed 11 years ago
Icons appear as missing Unicode characters
Categories
(Web Compatibility :: Site Reports, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jaclemire, Unassigned)
Details
Attachments
(4 files)
User Agent: Mozilla/5.0 (X11; Linux i686; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20131211030206
Steps to reproduce:
Browse page http://www.neo4j.org/develop/drivers
Actual results:
Some icons on the top are not displayed as icon but as missing Unicode characters.
Expected results:
As displayed by Google Chrome, with the gears and the down arrow in the box.
Reporter | ||
Comment 1•12 years ago
|
||
![]() |
||
Comment 2•12 years ago
|
||
With 2013-12-11-03-02-06-mozilla-central-firefox-29.0a1.en-US.linux-x86_64, a locally installed font is used for them, so I see different characters. Works in Beta with my profile.
Component: Untriaged → Layout: Text
Product: Firefox → Core
Comment 3•12 years ago
|
||
(In reply to Jacques Lemire from comment #0)
> Created attachment 8346122 [details]
> Screenshot from 2013-12-11 15:51:07.png
>
> User Agent: Mozilla/5.0 (X11; Linux i686; rv:29.0) Gecko/20100101
> Firefox/29.0 (Beta/Release)
Where does this "Beta/Release" come from? Firefox 29 isn't on the Beta or Release channels; it's currently in Nightly.
> Build ID: 20131211030206
>
> Steps to reproduce:
>
> Browse page http://www.neo4j.org/develop/drivers
>
>
> Actual results:
>
> Some icons on the top are not displayed as icon but as missing Unicode
> characters.
>
>
> Expected results:
>
> As displayed by Google Chrome, with the gears and the down arrow in the box.
The icons (which use FontAwesome as a webfont) work for me in Nightly (29.0a1) on Ubuntu, as well as in earlier versions I tried.
Have you perhaps disabled downloadable fonts? Try a clean profile?
Reporter | ||
Comment 4•12 years ago
|
||
This morning reinstalled brand new version from:
http://nightly.mozilla.org/
Same wrong icons.
"Have you perhaps disabled downloadable fonts?" Where? How?
Comment 5•12 years ago
|
||
(In reply to Jacques Lemire from comment #4)
> This morning reinstalled brand new version from:
> http://nightly.mozilla.org/
>
> Same wrong icons.
>
> "Have you perhaps disabled downloadable fonts?" Where? How?
In about:config, check that gfx.downloadable_fonts.enabled is set to true.
Have you tried with a new profile? (If there's any setting, add-on, etc., in your profile that is affecting this, installing a new version of Nightly won't help, as you'll still be using the same profile.)
Reporter | ||
Comment 6•12 years ago
|
||
TO: Jonathan Kew
(1) gfx.downloadable_fonts.enabled was already set to true.
(2) For the profile: I took my courage in both hands and I created a profile. Same wrong icons.
(3) Restart installation: remove .cache and .mozilla. Same Icons.
Comment 7•12 years ago
|
||
I'm puzzled as to why it doesn't work for you, when it looks fine here.
Do webfonts work for you on other pages? E.g. if you go to http://fontdeck.com/font/olicana/rough, does the "handwritten" font specimen show, or do you just get a default typewriter-like font?
Are you connecting through a corporate network that may involve firewalls, proxies, etc., or are you connecting directly to the internet?
cc'ing jdaggett, in case he has any bright ideas here.
Reporter | ||
Comment 8•12 years ago
|
||
To: Jonathan Kew
No problem, I see the handwritten fonts.
Comment 10•12 years ago
|
||
If you install the fontinfo add-on,[1] and then look at the list of fonts used in the Page Info window, are -any- webfonts used on the neo4j.org page?
If you load the page with the Web Console open, are there any error or warning messages related to webfonts in the console? (Try this with a freshly-launched browser, to avoid font-caching issues.) I notice that it apparently first tries to load a .woff version of the FontAwesome font, then falls back to the .ttf version when this fails.
[1] https://addons.mozilla.org/en-US/firefox/addon/fontinfo/
Comment 11•12 years ago
|
||
Here's what I see with current Nightly (2013-12-13).
Reporter | ||
Comment 12•12 years ago
|
||
Reporter | ||
Comment 13•12 years ago
|
||
BTW I moved back to Fifefox beta -- it crashes all the time on the profile, but same problem with the icons.
Few lines form the web console:
08:51:18.938 downloadable font: download failed (font-family: "OfficinaSerifStd-Bold" style:normal weight:normal stretch:normal src index:1): bad URI or cross-site access not allowed
source: http://assets.neo4j.org/new/font/officinaserifstd-bold.woff main.css
08:51:18.988 Unknown property 'box-sizing'. Declaration dropped. drivers
08:51:19.093 downloadable font: download failed (font-family: "FontAwesome" style:normal weight:normal stretch:normal src index:1): bad URI or cross-site access not allowed
source: http://assets.neo4j.org/new/font/fontawesome-webfont.woff font-awesome.css
08:51:19.184 downloadable font: download failed (font-family: "OfficinaSerifStd-Bold" style:normal weight:normal stretch:normal src index:2): bad URI or cross-site access not allowed
source: http://assets.neo4j.org/new/font/officinaserifstd-bold.ttf main.css
08:51:19.184 downloadable font: no supported format found (font-family: "OfficinaSerifStd-Bold" style:normal weight:normal stretch:normal src index:4)
source: (end of source list) main.css
08:51:19.300 downloadable font: download failed (font-family: "FontAwesome" style:normal weight:normal stretch:normal src index:2): bad URI or cross-site access not allowed
source: http://assets.neo4j.org/new/font/fontawesome-webfont.ttf font-awesome.css
08:51:19.301 downloadable font: no supported format found (font-family: "FontAwesome" style:normal weight:normal stretch:normal src index:4)
source: (end of source list) font-awesome.css
08:51:19.387 Error in parsing value for 'position'. Declaration dropped.
Comment 14•12 years ago
|
||
Ah, so the fonts hosted at assets.neo4j.org are apparently being blocked, because assets.neo4j.org is a different origin than www.neo4j.org, and @font-face doesn't allow cross-origin resource access unless the server is configured to use CORS to permit it.
In that case, this looks like it's an authoring problem on the site: to use fonts from a different origin, it's necessary to configure CORS appropriately. (Chrome won't show the problem because it doesn't follow the CSS Fonts spec requirement[1] here.)
What I don't understand, then, is why the fonts -do- work for me. I see a message about a failure for fontawesome-webfont.woff, but fontawesome-webfont.ttf and officinaserifstd-bold.woff load fine, as shown in attachment 8347399 [details]. Is there something unreliable about our cross-origin check?
jdaggett, do you have any idea what's going on here? Do the fonts work for you, or are they blocked?
[1] http://www.w3.org/TR/css-fonts-3/#font-fetching-requirements
Flags: needinfo?(jdaggett)
Comment 15•12 years ago
|
||
The icon font used is defined in the font named "FontAwesome". The stylesheet defines it this way:
src: url('../font/fontawesome-webfont.eot?#iefix') format('eot'),
url('../font/fontawesome-webfont.woff') format('woff'),
url('../font/fontawesome-webfont.ttf') format('truetype'),
url('../font/fontawesome-webfont.svg#FontAwesome') format('svg');
Enabling 'fontdownloader' and 'userfonts' logging, I see the following log entries related to this font:
userfonts (123fb3860) added (FontAwesome) with style: normal weight: 400 stretch: 0
fontdownloader (1639a1150) download start - font uri: (http://assets.neo4j.org/new/font/fontawesome-webfont.woff) referrer uri: (http://assets.neo4j.org/new/css/font-awesome.css)
userfonts (123fb3860) [src 1] loading uri: (http://assets.neo4j.org/new/font/fontawesome-webfont.woff) for (FontAwesome)
fontdownloader (1639a1150) download failed - font uri: (http://assets.neo4j.org/new/font/fontawesome-webfont.woff) error: 805303f4
userfonts (123fb3860) downloadable font: download failed (font-family: "FontAwesome" style:normal weight:normal stretch:normal src index:1): bad URI or cross-site access not allowed
source: http://assets.neo4j.org/new/font/fontawesome-webfont.woff
fontdownloader (165319b50) download start - font uri: (http://assets.neo4j.org/new/font/fontawesome-webfont.ttf) referrer uri: (http://assets.neo4j.org/new/css/font-awesome.css)
userfonts (123fb3860) [src 2] loading uri: (http://assets.neo4j.org/new/font/fontawesome-webfont.ttf) for (FontAwesome)
fontdownloader (165319b50) download completed - font uri: (http://assets.neo4j.org/new/font/fontawesome-webfont.ttf)
userfonts (123fb3860) [src 2] loaded uri: (http://assets.neo4j.org/new/font/fontawesome-webfont.ttf) for (FontAwesome) gen: 00000009
fontdownloader (165319b50) reflow
The 805303f4 error code indicates a bad URI error, not some cross-site problem. And it only occurs for the woff file, not for the ttf. So maybe this is somehow specifically related to Linux? The testpage displays just fine in latest Nightly under both OSX 10.8 and Win7.
Flags: needinfo?(jdaggett)
Comment 16•12 years ago
|
||
To enable the logging above:
export NSPR_LOG_FILE=/path/to/userfonts.log
export NSPR_LOG_MODULES=fontdownloader:5,userfonts:5
Then run nightly and load the testpage URL. Quit and you should see a logfile containing logging for all the font loads.
Comment 17•12 years ago
|
||
I get an error for both .woff and .ttf files, and not just fontawesome-webfont.*
but also officinaserifstd-bold.ttf and other fonts.
gdb tells me it's nsCORSListenerProxy::CheckRequestApproved that fails
to find "Access-Control-Allow-Origin", making nsCORSListenerProxy::OnStartRequest
return NS_ERROR_DOM_BAD_URI.
This seems like the expected result since the reply doesn't have that header:
# wget -S --referer='http://www.neo4j.org/assets/new/css/main.css' http://assets.neo4j.org/new/font/officinaserifstd-bold.woff
--2013-12-17 17:00:12-- http://assets.neo4j.org/new/font/officinaserifstd-bold.woff
Resolving assets.neo4j.org (assets.neo4j.org)... 54.230.96.11, 54.230.96.142, 54.230.96.175, ...
Connecting to assets.neo4j.org (assets.neo4j.org)|54.230.96.11|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
Content-Type: application/octet-stream
Content-Length: 24788
Connection: keep-alive
Date: Wed, 23 Oct 2013 06:37:04 GMT
Last-Modified: Fri, 08 Mar 2013 10:57:21 GMT
ETag: "392135300f3d80f5931667501dc6a22c"
Accept-Ranges: bytes
Server: AmazonS3
Age: 28153
X-Cache: Hit from cloudfront
Via: 1.1 f735ed4dc89085e1a258a18cc75d1a51.cloudfront.net (CloudFront)
X-Amz-Cf-Id: OXrYfy4I10EiA8LBGKRC8oFEoeIC4bOhrKb5cIQa-P2A8troxPF90g==
Length: 24788 (24K) [application/octet-stream]
Comment 18•12 years ago
|
||
I also see the error as reported in Nightly on OSX, so it's not just Linux.
So I agree with Jonathan that this is a problem on the server.
-> Evang
Assignee: nobody → english-us
Component: Layout: Text → English US
Product: Core → Tech Evangelism
Version: 29 Branch → unspecified
![]() |
||
Comment 19•11 years ago
|
||
The site design has changed.
Assignee: english-us → nobody
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Component: English US → Desktop
Resolution: --- → INVALID
Assignee | ||
Updated•6 years ago
|
Product: Tech Evangelism → Web Compatibility
You need to log in
before you can comment on or make changes to this bug.
Description
•