Open Bug 1410374 Opened 4 years ago Updated 3 years ago

sone fonts can't be selected

Categories

(Core :: Layout: Text and Fonts, defect, P3)

58 Branch
defect

Tracking

()

UNCONFIRMED
Tracking Status
firefox56 --- wontfix
firefox57 --- wontfix
firefox58 --- wontfix
firefox59 --- ?

People

(Reporter: lilydjwg, Unassigned)

References

Details

(Keywords: regression)

Attachments

(3 files)

Attached file simple demo page
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0
Build ID: 20171019100107

Steps to reproduce:

I set text font to Lucida Handwriting, Lucida Calligraphy or IM FELL English.


Actual results:

The text is rendered in the default font DejaVu Sans Oblique.


Expected results:

The text should be rendered in the specified fonts.

This works with Firefox 52 ESR. The former two work with Google Chrome.
Component: Untriaged → Layout: Text
Product: Firefox → Core
I tried mozregression and it tells me 2015-05-13 is good and 2015-05-14 is bad, with an empty profile.
This is a result of bug 1056479, though offhand I'm not sure exactly why it's failing in this way.

If you remove the font-style:italic from your test page, does that make any difference?
Flags: needinfo?(lilydjwg)
Removing font-style:italic doesn't help: it renders in DejaVu Sans. I added them because in the past Firefox wouldn't render in Lucida Handwriting and Lucida Calligraphy without that.

BTW, you can find the IM FELL English font in Google Fonts. And Firefox renders correctly with web fonts. (The local file was downloaded from there too. I tried to remove the old woff font file and place a new ttf one downloaded just now and it doesn't make a difference.)
Flags: needinfo?(lilydjwg)
Priority: -- → P3
Has Regression Range: --- → yes
I'm uploading screenshots for http://zipcon.net/~swhite/docs/computers/browsers/fonttest.html, a great page for testing fonts.

You can see that Firefox (today's nightly) nearly renders all text in DejaVu Serif while Google Chrome is doing as expected.
firefox-52 went EOL, so there are no current firefox versions that doesn't trigger that bug it seems :(
You need to log in before you can comment on or make changes to this bug.