Some MacOS Sierra fonts not used and fallback to next font
Reported by
murak...@vivliostyle.com,
Oct 27 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36 Example URL: http://blog.fonland.net/2016/09/new-fonts-macos-sierra.html Steps to reproduce the problem: 1. Open the specified URL 2. Open the inspector and see rendered font for lines such as "font-family: YuKyokasho" What is the expected behavior? YuKyokasho (or other specified family) is used to render the text. What went wrong? Hiragino Mincho is used. 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: 54.0.2840.71 Channel: stable OS Version: OS X 10.12.1 Flash Version: Shockwave Flash 23.0 r0 This seems Sierra only problem.
,
Oct 27 2016
,
Nov 16 2016
,
Nov 17 2016
> Does this work in other browsers? Yes Would you have a screenshot or other data that suggests this does actually work in other browsers? Some of the new fonts like YuKyokasho, Hanzipen et. are not placed in the regular font directories, but instead in /System/Library/Frameworks/ApplicationServices.framework/Frameworks//ATS.framework/Support/FontSubsets/ I could not get Safari or FF to match against those, and in my experiments they cannot be selected in TextEdit as fonts to format text either.
,
Nov 17 2016
Right, so for my English UI system, I had to manually click the download button and download the YuKyokasho and Hanzipen in Font Book, then font matching starts to work in Safari stable. Chrome needs a modification of the sandbox rules.
,
Nov 17 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by tkent@chromium.org
, Oct 27 2016