[wp-trac] [WordPress Trac] #46169: Use system fonts for the block editor
WordPress Trac
noreply at wordpress.org
Wed Feb 6 02:14:51 UTC 2019
#46169: Use system fonts for the block editor
--------------------------------------+-----------------------------------
Reporter: garrett-eclipse | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Editor | Version: 5.0
Severity: normal | Resolution:
Keywords: needs-patch needs-design | Focuses: performance, privacy
--------------------------------------+-----------------------------------
Changes (by pento):
* keywords: needs-patch => needs-patch needs-design
Comment:
Replying to [ticket:46169 garrett-eclipse]:
> 1. From a privacy standpoint Google Fonts tracks users potentially
collecting PII
Is there a reference for this? Reading through
[https://github.com/google/fonts/issues/1495 this discussion] and
[https://developers.google.com/fonts/faq#what_does_using_the_google_fonts_api_mean_for_the_privacy_of_my_users
the related FAQ], it seems like Google logs minimal data from Google Fonts
requests.
> 2. From a performance standpoint the assets should be served locally to
take advantage of modern font-loading optimization, etc. The cross-domain
request slows down the site even with pre-fetching.
Google Fonts is pretty fast. The first request to load the block editor
from my site takes ~8s, of which 80ms is Noto Serif. Subsequent loads are
4s for the page load, and 0ms for Noto Serif, thanks to caching. This
seems like a premature optimisation.
I'll defer to the design team as to whether system fonts are a better (or
at least equivalent) writing experience compared to Noto Serif.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/46169#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list