Inconsistency in Google Fonts Activation Status

[okmttdhr]

Description

After successfully activating and installing the Google Fonts asset, there is an inconsistency in the font's selection status. Despite receiving a success message indicating that the font was installed correctly, the user interface displayed the font as unchecked or unselected, suggesting it had not been chosen.

Expected Behavior:
The font should appear as selected or checked off immediately after installation, reflecting the success message.

Actual Behavior:
The font appears unchecked or as if it hadn't been selected despite the success message. However, upon navigating back to the Library tab, the font is listed as Active.

Step-by-step reproduction instructions

• Open the Font Library modal
• Select the Install Fonts tab
• Click one of Google Fonts and check some variations
• Click the Install button
• Observe the success message confirming the font's installation.
• Observe that the font appears unchecked
• Select the Library tab
• Observe that the fonts are active

Screenshots, screen recording, code snippet

Environment info

• Gutenberg > 17.6

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

[arthur791004]

The condition of “checked” seems to be different from the “Library” and ”Install Fonts“.

• The “Library” checks whether the font variant is installed or activated. See

  gutenberg/packages/edit-site/src/components/global-styles/font-library-modal/library-font-variant.js

  Line 51 in 7472c0d

  checked={ isInstalled }

• The “Install Fonts” checks whether the font variant is in outline. See

  gutenberg/packages/edit-site/src/components/global-styles/font-library-modal/collection-font-details.js

  Line 43 in 7472c0d

  selected={ isFontFontFaceInOutline(

I guess it's the expected behavior but the user may feel confused 😅

[annezazu]

This feels related to this issue: #58276 Perhaps we can consolidate there to think about the entire experience?

[colorful-tones]

This also overlaps with #58989 and considerations around UI/UX could impact both of these.

[ironprogrammer]

IMHO this is the same as #58989, which has a bit more recent activity and design discussion going on.

@okmttdhr, would you mind if this issue was closed and continued to be tracked over in #58989?

[arthur791004]

Sure. Let's close this one in favor of #58989 🙂