Issue metadata
Sign in to add a comment
|
Local fonts incorrectly used instead of web fonts
Reported by
ben.lubar@gmail.com,
May 21 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36 Example URL: https://jsfiddle.net/dtesw1yj/1/ Steps to reproduce the problem: 1. Download Roboto[1] from Google Fonts. 2. Install Roboto-Light.ttf. Make sure you have no other Roboto variants installed. 3. Restart Chrome and visit this page. [1] https://fonts.google.com/specimen/Roboto What is the expected behavior? All three lines are using different font weights. What went wrong? The middle weight (400) uses Roboto-Light (300). Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 66.0.3359.181 Channel: stable OS Version: 10.0 Flash Version:
,
May 22 2018
,
May 22 2018
also reported here https://github.com/google/fonts/issues/1568 you can see the problem on this page, attached are Chrome vs Firefox desktop screenshots (Win 10 build 1803) https://support.google.com/pixelphone/answer/7106961?hl=en&ref_topic=7084391
,
May 25 2018
Are you aware of this drott?
,
May 28 2018
Yes, I believe in this case, Google fonts does send CSS for font family: "Roboto", but src: local("Roboto Light"). Then a src: local() line is used, a uniquely identified local fonts should be selected, and no other style matching performed. I think this might be the reason leading to font mismatching here. I am going to merge this particular issue into the larger effort of fixing our local() matching.
I think Google Fonts' CSS here is a compromise, but without us fixing issue 627143 in Chrome, it's hard to make the matching more precise.
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ben.lubar@gmail.com
, May 21 2018