Chrome selects incorrect font weight for font-weight: 500 when using Source Sans Pro
Reported by
john.rey...@mavens.co.uk,
Jun 15 2017
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Install the widely used open source Source Sans Pro ttf fonts https://github.com/adobe-fonts/source-sans-pro 2. Create a web page with text with CSS style: font-family: "Source Sans Pro"; font-weight: 500; 3. View the font on the page and in the computed tab in the developer tools under the rendered fonts. What is the expected behavior? The font selected should be the regular weight: Fonts available are the regular font at weight 400 according to the OS/2 metadata, and semibold at 600. According to the CSS spec for missing weights: If the desired weight is 500, 400 is checked first and then the rule for desired weights less than 400 is used. What went wrong? Chrome instead selects the 600 weight semibold font. 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: 59.0.3071.86 Channel: stable OS Version: 10.0 Flash Version: FireFox and Edge both select the regular font.
,
Jun 16 2017
Thanks for reporting the issue. @john.reynolds-- Could you please provide us the sample webpage url or testcase , where you can reproduce the issue and also please help us by providing the expected result screenshot , that would help us in triaging the issue better. Thanks!
,
Jun 16 2017
Attached test case and screenshots from Chrome and FireFox (which I believe is getting it right).
,
Jun 16 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 19 2017
,
Jun 19 2017
Tested the issue on windows 10 using chrome M59 #59.0.3071.104 and observed behavior as attached in screenshot with the steps below: 1. Launched given html file in chrome and opened devtools and observed the rendered fonts in Times new roman. @john.reynolds-- Could you please check attached screenshot and confirm us if this is the issue you are facing and please let us know if we had missed any steps in reproducing the issue. Thanks!
,
Jun 19 2017
No, you first need to do the step 1. in the original report, which is to install the fonts locally (this issue is likely also relevant to the webfont version, but I've not actually tested that). To install these, you'll need the latest release from the github page linked above, and extract the fonts from the TTF directory, and install them (from the right click menu on windows). As open source fonts, these are also available from most of the usual font sites such as fontsquirrel.
,
Jun 19 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 19 2017
And further details in case that wasn't clear: 1. Get the zip file: https://github.com/adobe-fonts/source-sans-pro/releases/latest 2. Extract the files from this. 3. Open the top folder of this, and in that there should be a TTF folder. 4. Within the TTF folder, select all the .TTF fonts, right-click on the them and select install.
,
Jun 19 2017
The result I get from that, is the font in the developer tools being "Source Sans Pro Semibold" where I'd expect "Source Sans Pro".
,
Jun 19 2017
,
Dec 15 2017
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by chrishtr@chromium.org
, Jun 15 2017