If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Google Poppins font not rendering properly in firefox while its installed in pc

NEW
Unassigned

Status

()

Core
Graphics: Text
P3
normal
a year ago
2 months ago

People

(Reporter: hardik.vyas, Unassigned)

Tracking

47 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [gfx-noted], URL)

Attachments

(1 attachment)

(Reporter)

Description

a year ago
Created attachment 8763854 [details]
poppins.jpg

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Steps to reproduce:

Google Poppins fonts installed.


Actual results:

Google Poppins font display much bolder in firefox. 
When its uninstalled from pc. It works properly.



Expected results:

It should be proper as per other browsers.
(Reporter)

Comment 1

a year ago
It happens with Poppins Regular/Normal fonts.
Component: Untriaged → Graphics: Text
Product: Firefox → Core
I see the same problem on Mac OS X. It appears the use of src:local('Poppins') is finding the bold face instead of the expected Regular one.

This doesn't happen if the locally-installed Poppins fonts are used directly via font-family; it's only when @font-face rules with src:local() come into play. Not sure yet why it's finding the wrong face in this instance...
Status: UNCONFIRMED → NEW
Ever confirmed: true
Ah, got it. It's an error in the Poppins-Bold.ttf font.... it has a PostScript name (ID 6 in the 'name' table) of "Poppins", which is the same as the Full name (ID 4) in the Poppins-Regular.ttf font. And local name lookup checks for both psname and fullname (as per spec[1]), which means either of these faces is a match for src:local("Poppins"), as found in the Google Fonts CSS.

The fix is for the Bold font to be given the proper PSname "Poppins-Bold" in its 'name' table, so that it doesn't conflict with the regular face.

Given the ambiguity created by the bad font name, the problem may or may not show up in any given browser. This will depend whether it checks both fullname and psname (as CSS-Fonts says) or only one of them, and depending on the particular order it happens to search the available fonts.

So this issue should be reported to the Poppins font developers; it's not a Firefox bug.

[1] https://www.w3.org/TR/css-fonts-3/#src-desc
Whiteboard: [gfx-noted]
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.