Font Face: Adds a GB specific resolver to capture changes not yet in Core #54990
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Adds and uses
Gutenberg_Font_Face_Resolver_6_4
.Why?
Font Face is already merged into WordPress Core. Since it loads before the plugin, the plugin's Font Face files do not get loaded into memory. Thus any changes made or needed will not get loaded when WP 6.4 or Core's
trunk
is used (such as in the test suite).By having a duplicate of the resolver that is for the plugin only, this new resolver does get loaded into memory and is used when not running WP 6.4 or Core's
trunk
. Thus all changes get tested.How?
trunk
, it unhooks Core'swp_print_font_faces
callback, adds a GB specific callback, invokes the new resolver, and then passes the results towp_print_font_faces()
.Testing Instructions
All CI jobs should pass.
And the
fonts
tests should pass when running: