Add input with save button

[grzim]

What problem does this address?

In Navigation Editor, when a menu name is changed, a user needs to hit the save button in order to apply the change. This is not obvious action and is not UX-friendly.

What is your proposed solution?

As proposed by @shaunandrews we can add a component with a save button inside an input. This will make a saving action more straightforward.

[paaljoachim]

What about adding in a button that says save?

[grzim]

@paaljoachim currently we have a save button that saves configuration from the navbar.
However, as mentioned in comment, it is not obvious for a user, they need to click on save therefore it would be better to introduce this component.

But on the other hand, we would end up in the situation, when only menu rename has its own button to save, whereas the rest of the config in the same area is saved all with one button.
This could lead to confusion as well.

@shaunandrews I will be grateful if you can share your thoughts on this.

[talldan]

I noticed there's one just like this in the LinkControl component when editing a link:

But it doesn't look particularly easy to extract this into a general purpose component. There's quite a bit going on.

[shaunandrews]

I think if we improve our handling of unsaved changes as outlined in #30322 we won't need to have a discrete save button for the menu name.

[grzim]

Thanks for your feedback @shaunandrews