Bug 1303585 - Firefox 44 does not use the Open Sans regular font
Summary: Firefox 44 does not use the Open Sans regular font
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-01 11:35 UTC by Matthew Ames
Modified: 2016-02-05 12:11 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-02-05 12:04:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screenshot showing comfortaa being used instead of open sans (132.13 KB, image/png)
2016-02-01 11:35 UTC, Matthew Ames
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 1245082 0 None None None 2016-02-02 13:32:45 UTC

Description Matthew Ames 2016-02-01 11:35:01 UTC
Created attachment 1120073 [details]
Screenshot showing comfortaa being used instead of open sans

Description of problem: When using Open Sans Regular as the Interface font set by gnome-tweak-tool, firefox 44 does not draw this font, and instead renders comfortaa


Version-Release number of selected component (if applicable): 44


How reproducible: 100%


Steps to Reproduce:
1. Install brand new fedora 23.
2. Install open-sans-fonts.
3. ensure firefox upgraded to 44
4. run `gsettings set org.gnome.desktop.interface document-font-name 'Open Sans 10'` to change the font to opensans
5. open firefox and note the tabs and url bar show the wrong font

Actual results:
Font comfortaa is used. See attached screenshot from configured system in gnome-boxes


Expected results:
Open Sans should be used

Additional info:
This has been witnessed in passing on two separate machines, and tested fully on another.

Comment 1 Matthew Ames 2016-02-05 12:04:01 UTC
Bug is being fixed upstream in https://bugzilla.mozilla.org/show_bug.cgi?id=1245811


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