-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Webfonts] Rename to Fonts API #46749
Conversation
1e6b6fe
to
be55e3a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this, @hellofromtonya! I've left a few notes for review.
Well darn it all, lots has changed since I created this PR. Merge conflicts are being unruly. Going to rebase and reapply the commits. Then force push to get it back in sync. Then will apply the changes @ironprogrammer suggested (thank you Brian). |
* Moves the files into a fonts-api directory to better identify all of the API's files. * Moves the deprecated files (BC layer) into a /deprecations/ dir to better identify files that will not be backported to Core.
805b8fa
to
145548e
Compare
145548e
to
79cc093
Compare
79cc093
to
52ef0d6
Compare
@ironprogrammer @aristath It's ready for your review and testing. If possibly, would like to merge this PR this week to unblock the rest of the API's work. Thanks! |
Flaky tests detected in 79cc093432d018bb738888d9dcf6f13dbcd37cea. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/3943813274
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing work here! Looks good to me and works as advertised 👍
Closes #42868.
What?
Renames the API from Webfonts to Fonts API.
Why?
The renaming is to align the feature to well-known authoritative standards for consistency and maintainability. Why? These standards do not use "webfont" to describe
@font-face
CSS styles. Rather, they use terms such as "font", "custom font", "downloadable font", and "web font".How?
Testing Instructions
Testing Instructions for Keyboard
Testing Instructions
@font-face
stylings in the admin area by:wp-fonts-local
(which is in the<head>
)<style>
element to inspect the CSSwp-fonts-local
<style>
element to inspect the CSSwp-fonts-local
<style>
element to inspect the CSS and verify the CSS.Testing a plugin
This gist is a plugin that uses Jetpack's Google Font Provider package, which is using the original (deprecated) API functionality and web fonts array structure. So it should continue to work and throw deprecation notices.
Instructions of how to install and test are in the plugin's
README.md
file, which you can get here.Note: This plugin has a Google Fonts Provider which means it will print
<style id="wp-fonts-jetpack-google-fonts">..</style>
into the<head>
.