Font Face: backport from Core changeset 56500

[hellofromtonya]

What?

Font Face was merged into Core by changeset 56500. This PR backports the changes from Core.

Why?

To keep Core and Gutenberg files in synchronized.

How?

• Merges the changes made in Core while retaining plugin specifics.
• Adds @core-merge notes where appropriate.

Review notes:

When comparing the changes from Core's changeset 56500, please note that it included the static instance in wp_print_font_faces(). This static was removed in Gutenberg via commit 98b331e and in Core via changeset 56540.

Tip: Compare the changes from the code that's in Core's trunk, i.e. to avoid confusion of the static change.

[github-actions]

This pull request has changed or added PHP files. Please confirm whether these changes need to be synced to WordPress Core, and therefore featured in the next release of WordPress.

If so, it is recommended to create a new Trac ticket and submit a pull request to the WordPress Core Github repository soon after this pull request is merged.

If you're unsure, you can always ask for help in the #core-editor channel in WordPress Slack.

Thank you! ❤️

View changed files

❔ lib/compat/wordpress-6.4/fonts/font-face/class-wp-font-face-resolver.php
❔ lib/compat/wordpress-6.4/fonts/font-face/class-wp-font-face.php
❔ lib/compat/wordpress-6.4/fonts/fonts.php
❔ phpunit/tests/fonts/font-face/base.php
❔ phpunit/tests/fonts/font-face/wpFontFace/generateAndPrint.php
❔ phpunit/tests/fonts/font-face/wpFontFaceResolver/getFontsFromThemeJson.php
❔ phpunit/tests/fonts/font-face/wpPrintFontFaces.php

[github-actions]

Flaky tests detected in 877d725.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/6114287700
📝 Reported issues:

• [Flaky Test] should not allow blocks to be inserted in inner blocks #44341 in specs/editor/plugins/cpt-locking.test.js

[anton-vlasenko]

I've reviewed these changes, and they seem to be in line with what's already committed to Core.

I did a quick test and didn't notice any errors.

Therefore, I approve this PR.

[github-actions]

Warning: Type of PR label error

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Accessibility (a11y), [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core.
• Labels found: [Type] Enhancement, Backport from WordPress Core, [Feature] Typography.

Read more about Type labels in Gutenberg.