WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #36753, comment 32


Ignore:
Timestamp:
05/18/2016 10:55:27 PM (3 years ago)
Author:
mattmiklic
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36753, comment 32

    initial v1  
    22> We will need to start being much more careful about usage of font weights since there may be variations across systems. My suggestion would be to update our CSS guidelines to require use of numerical font-weights. We also need to audit current uses and adjust them accordingly. Should I create a new ticket for this, or can we do it here? Will need to happen in 4.6 since the change causes issues at least in one spot so far.
    33
    4 Auditing current usage and standardizing on a handful of weights is a good idea. When I initially made this change on WordPress.com, I noticed in a few places, fonts were displaying super-thin or super-thick, because they'd been specified with a font-weight of something like 100 or 900 in CSS. Because only loaded the 300, 400, and 600 weights from Google, we never noticed until we switched back to system fonts.
     4Auditing current usage and standardizing on a handful of weights is a good idea. When I initially made this change on WordPress.com, I noticed in a few places, fonts were displaying super-thin or super-thick, because they'd been specified with a font-weight of something like 100 or 900 in CSS. Because we only loaded the 300, 400, and 600 weights from Google, we never noticed until we switched back to system fonts.
    55
    66The SF typeface on iOS and MacOS has nine weights. On Windows, there are five weights of Segoe UI. It's less of an issue on Android/ChromeOS, which only makes two weights (regular and bold) of Roboto available on the web (more weights are available in native Android apps, but only those two load in Chrome/Android). Not sure about the Linux flavors, off the top of my head.