697320 - opez.com - Firefox 7.0.1 renders the word "financial" as "nancial" in several places due to missing ligature glyph (bad font)

Status: RESOLVED INVALID

(Web Compatibility :: Site Reports, defect)

Description

[GeoFan49]

Attachment: firefox-vs-safari-mac--rendering-financial-as-nancial.jpg

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
Build ID: 20110928134238

Steps to reproduce:

Go to the website http://opez.com/bob using firefox 7.0.1 on Mac (Mac OS X 10.6.8)


Actual results:

See the word FINANCIAL rendered as NANCIAL on several places on that web page.  The HTML seems normal.


Expected results:

The word FINANCIAL should be rendered properly.

Comment 1

[philippe (part-time)]

I see the same with a recent nightly (10.0a1 (2011-10-22)). There is something wrong with the font used - font-family: NimbusSanNov-Med; (web font)

Comment 2

[Jonathan Kew [:jfkthame]]

Attachment: screenshot of the glyph repertoire in NimbusSanNov

It's a broken font; the author should complain to his font provider (myfonts.com).

The problem is that in this font many glyphs - basically everything except the Latin-1 set, I think - have been replaced with blanks, but the OpenType tables that implement things like the "fi" ligature are still present. As Firefox supports OpenType ligatures, it (correctly) replaces the sequence <f, i> with the <fi> glyph - which is blank.

The attached screenshot shows the glyph palette of the font, with many glyphs - including the f-ligatures - being blank.

Comment 3

[Jonathan Kew [:jfkthame]]

Moving to Tech Evangelism, as this is not a Gecko/Firefox bug; it needs to be fixed by the font provider.

I've written to a contact at myfonts.com to point out the problem.

Comment 4

[Alice0775 White]

Regression window:
Works:
http://hg.mozilla.org/mozilla-central/rev/69c86f3acc5a
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2a1pre) Gecko/20090224 Minefield/3.2a1pre ID:20090224033722
Fails:
http://hg.mozilla.org/mozilla-central/rev/8eba35e62d92
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2a1pre) Gecko/20090225 Minefield/3.2a1pre ID:20090225033705
Pushlog:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=69c86f3acc5a&tochange=8eba35e62d92

Triggered by
d08d06bdd4c9	John Daggett — Bug 475164 - accept fonts that have null name records. r=vlad

Why Google Chrome display correctly? and Firefox not?

Comment 5

[philippe (part-time)]

(In reply to Alice0775 White from comment #4)
 
> Why Google Chrome display correctly? and Firefox not?

Because ligatures are not turned on by default in WebKit. If you add 'text-rendering: optimizeLegibility;' to the root element through the WebKit inspector, you'll see the same issue.

(note that on Gecko 1.9.2, OS X 10.6.8, it does display the 'fi' 'correctly', but it falls back on the default font)

Comment 6

[Alice0775 White]

(In reply to philippe from comment #5)
> (In reply to Alice0775 White from comment #4)
>  
> > Why Google Chrome display correctly? and Firefox not?
> 
> Because ligatures are not turned on by default in WebKit. If you add
> 'text-rendering: optimizeLegibility;' to the root element through the WebKit
> inspector, you'll see the same issue.
> 
Thanks

> (note that on Gecko 1.9.2, OS X 10.6.8, it does display the 'fi'
> 'correctly', but it falls back on the default font)

Why Firefox3.6.23  does not fall back on window?
Why Firefox7.0 and later version do not  fall back ?

Comment 7

[Jonathan Kew [:jfkthame]]

My contact at MyFonts.com has acknowledged the problem, and says they're working on an improved toolset.

Meanwhile, there's no need for further technical investigation here; it's clear that this is a font error, not a Firefox bug.

The site author should either change fonts, or deploy a corrected version - the simplest fix would be to strip the OpenType layout tables from the font, or to avoid "subsetting" by blanking out many glyphs.

(Another possible workaround might be to add "-moz-font-feature-settings: 'liga=0'" to the site's CSS, so as to explicitly turn off default ligatures.)

Comment 8

[John Daggett (:jtd)]

Testcase that shows the problem in Firefox/Safari/Chrome:
http://people.mozilla.org/~jdaggett/tests/bug697320.html

Includes text-rendering to enable ligatures in Safari/Chrome.

Sent a message to the page owner.

Comment 9

[Chris Lawson (gone)]

TE bugs shouldn't generally be resolved INVALID, especially when there's something the site is doing wrong (see comment 7).

Comment 11

[Karl Dubost💡 :karlcow]

Hmm no luck this morning.

> Under Maintenance
> Hey there — we apologize, but Opez is currently under maintenance. 
> If you have any pressing issues, please feel free to reach out to us: [e-mail].

Let's see
The site was already on Maintenance on March 8, 2013.
http://web.archive.org/web/20130308023028/http://opez.com/bob

Let's close it as INVALID.