Shortcut Ctrl + S not saving dictionary items

[deekoulos]

Which Umbraco version are you using?

16.3.0

Bug summary

With the v16.3 keyboard shortcuts were reintroduced to the back office. However, although Ctrl + S works well on content nodes, it's not working on updating dictionary items. However, it works for the initial creation of the dictionary items.

Specifics

No response

Steps to reproduce

1. Login to BO
2. Navigate to Translations
3. Create a dictionary item with key and value
4. Save by clicking on the green save button (do not Ctrl + S here)
5. Change the value for the dictionary item
6. Try to save by pressing Ctrl + S

Expected result / actual result

Updating the dictionary item value should be saved correctly.

[github-actions]

Hi there @deekoulos!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[NguyenThuyLan]

I can see the problem here, when the mouse is still in the input box and you press ctrl s it won't work, this error happens even on content or other location.
I was able to reproduce this issue on v17-beta and v16.3.1

[nielslyngsoe]

This is fixed by this PR #20605, which will take part in version 16.4 and 17.0