Bug 1409348 - Some fonts (such as Droid Sans) don't work anymore on some websites with Firefox
Summary: Some fonts (such as Droid Sans) don't work anymore on some websites with Firefox
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-01 03:31 UTC by Jean-François Fortin Tam
Modified: 2017-12-12 10:19 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:19:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jean-François Fortin Tam 2017-01-01 03:31:38 UTC
Screenshot: https://bug1257709.bmoattachments.org/attachment.cgi?id=8731947

Sample website: http://jeff.ecchi.ca
This website uses the Droid Sans fonts, but somehow Firefox 

I had originally filed a bug on Firefox at https://bugzilla.mozilla.org/show_bug.cgi?id=1257709 but from what I can see now this is actually a bug that is specific to Fedora—either Fedora's version of Firefox, or Fedora's version of the Google Droid fonts:

- The issue does not occur on Firefox on other OSes
 (OpenSUSE Tumbleweed, Ubuntu, Mac OS X).

- The issue does not occur if you do "dnf remove google-droid*"

Comment 1 Danny Brodzik 2017-03-17 00:58:04 UTC
I can confirm this on Fedora 25 with the latest updates. I also have problems with Open Sans.

Comment 2 Jean-François Fortin Tam 2017-05-09 02:36:50 UTC
So maybe something with font rendering (freetype?) itself, or Fedora's Firefox package? Nicolas, any pointers on how we could know with more certainty?

Comment 3 Nicolas Mailhot 2017-05-09 08:41:23 UTC
It's almost certainly a bug in the Firefox font handling code

Fedora uses a lot of substitution rules in fontconfig, in particular for Droid

They've been vetted by the fontconfig upstream maintainer before deployment and haven't changed for years (and the open sans package didn't follow those rules last time I checked leading to problems)

However, because they are advanced and complex, they've tripped implementation bugs in apps that do stuff with fonts in the past (for example QT) when upstream didn't implement properly all the fontconfig substitution logic. IIRC Suse and Ubuntu do not push fontconfig as hard as Fedora, so they won't hit the same application bugs.

Comment 4 Fedora End Of Life 2017-11-16 18:53:27 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2017-12-12 10:19:31 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.