[wp-trac] [WordPress Trac] #49191: Twenty Twenty: Chrome displays glyphs instead of "Hoefler Text" or fallback fonts

WordPress Trac noreply at wordpress.org
Mon Jan 13 17:25:38 UTC 2020


#49191: Twenty Twenty: Chrome displays glyphs instead of "Hoefler Text" or fallback
fonts
--------------------------+-----------------------------
 Reporter:  jaruzek       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Themes        |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 In macOS Catalina, using Chrome 79, fonts in both the block editor and
 frontend display as Glyphs, rather than readable text.

 Disabling the following fonts rectifies this:
 NonBreakingSpaceOverride,"Hoefler Text"

 [[Image(https://d.pr/i/r7P7Y6/kN4TqhjxNq+)]]

 It appears that "Hoefler Text" is the contentious font in my case, despite
 it not being installed on my system.

 My initial suspicion was that it was was due to the following fonts, which
 may still have some relevance: -apple-system, BlinkMacSystemFont


 What I expected

 - Fonts in Twenty Twenty to render in a human-readable fashion

 What happened instead

 - Fonts rendered as glyphs
 - Text became legible after editing/turning off font stack, as per the
 screenshot above

 Browser / OS version

 - Chrome 79 on macOS 10.15.2
 - This issue does not appear in Chrome Canary v81, so it might be a
 browser issue
 - Colleagues using Chrome 79 could not reproduce this issue

 #### Screenshot / Video

 [[Image(https://d.pr/i/wmfavw/XFOOFDpcyW+)]]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49191>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list