-
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
Font Library: Uploaded fonts do not always display correctly until after page refresh #55018
Comments
I experience this too. In my case, it seems the intermittent behavior primarily happens to display fonts type (Google font classification: display). The fonts are properly display if I choose: technology (variable), decorative style (sans serif), classification (any) e.g. Montserrat, Open Sans and Space Grotesk. But the problem appears if I select technology (variable), decorative style (sans serif), classification (display) e.g. Tilt Neon, Big Shoulders Stencil Display and Pixelify Sans. Environment info:Windows 11 ver. 22H2 |
One reason for this problem may be that the added font's Figure 1: Immediately after uploading the Figure 2: After reloading the browser, you will see that |
I gave this a test just now, and it's fixed with #55393. Thanks everyone. |
Description
After uploading some custom fonts, the font management UI displays the new font name with a fallback font face (e.g. system serif font). Refreshing or navigating out and back to the editor resolves this, but I expect the newly uploaded font to be accurately represented in the UI without needing to refresh.
This behavior is intermittent, and can vary depending on the font. Here are some examples I tested (all fonts downloaded from Google Fonts for manual upload, except where noted):
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
Figure 1: Demonstration of font display after upload, then before and after refreshing the editor screen.
Environment info
trunk
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: