Font Library: No message appears when pressing the Update button

[t-hamano]

What problem does this address?

In the font library, for example, when you change the variation you use, you can click the Update button. When you click that button, the state is indeed saved, but no message is displayed.

What is your proposed solution?

In my opinion, there is a solution to either of the following:

• Use the Snackbar component to notify that settings have been properly updated.
• Remove Update button.

Personally, I prefer the latter approach. As I understand it, the behavior of the Update button has the same role as the Save button in the Global Styles. Also, the font variation setting is part of the global style.

I think whether or not to save changes made in global styles should be centralized in one button.

Screencast

7265fc7a03ca0dd6b4c87ee70be7c856.mp4

[madhusudhand]

@jasmussen Can you share your ideas on the messaging UI?

[jasmussen]

Yes, I touched on that in this PR review. I'm suggesting there do either of the following. Either when you press Update, the dialog is immediately closed, and the multi entity saving interface is opened, this one:

Or, when the Update button is pressed, you are taken to your library tab in the dialog. After all, you just enqueued it to be in your library.

I think we should avoid snackbars in this iteration, the basic flow should be in place before we add notices to explain.

[afercia]

Raising this issue to bug and adding the Accessibility label, as the lack of visible and audible feedback isn't ideal.

[akasunil]

A simple notice could work, in my opinion. We also use notice for font installation. Notice text can be something like Font settings were updated successfully

[t-hamano]

To ideally solve this problem, I think the first step would be to manage the notification as a state instead of context. The notification is only active on that screen and is supposed to be unmounted when the screen changes.

Currently, The notification is managed as a context, and notification status is preserved even when switching screens, so there is redundant processing to reset the notification status (example).

I will also address this issue as part of #58428.