Non-intuitive shortcut mapping

[julienallexandre]

Preliminary Checks

• I have read and understood the important section above.
• I have searched existing issues and avoided creating duplicates.
• I am not filing an enhancement request.
• I have checked that this issue cannot be reproduced on Mozilla Firefox.
• I have checked that this issue can be reproduced once I removed all my Mods and Custom CSS.

What happened?

It's impossible to easily swap two shortcuts

Expected behavior

It should be possible to change it normally without having to unset it and then reset it.

Actual behavior

Currently, we have to unset it and then set it again.

Steps to reproduce

When I go into the settings to set new shortcuts, it displays a warning saying that the shortcut is already taken, but when I swap two of them, it doesn't detect the change, so it keeps both as errors, and the shortcuts don't change. I have to unset one, then set the other, and then reset the second one again.

Screenshots and videos

Cap.2026-07-06.at.11.02.26.mp4

Version

1.21.5b (Firefox 152.0.4) (aarch64)

What platform are you seeing the problem on?

macOS - aarch64

What component is this issue related to?

Keyboard Shortcuts

Relevant log output if applicable

[ashvwinn]

It does not detect the change because the shortcut is never set if there is a conflict.
If you change shortcut A to B and B to A and they conflict with each other then its because shortcut A and B never changed and are the same as before.
If shortcut A had changed even on finding a conflict then it would mean there is a conflict and we just accepted it which would break the shortcut system.

Do you have any ideas to make this better without breaking the shortcut system?

[julienallexandre]

If I bind A to B, it should clear the key binding by indicating that it has been unbound and that I need to assign a different key (I'm using video games as an example).

[nickleigh05]

perhaps validate against what the other field is attempting, rather than its last saved key bind? This way it doesn't need to accept a conflict and it doesn't break the conflict system.

[EXOTARA]

Hi! I was able to reproduce this issue on Windows x64 using Zen [ 1.21.5b].

I also reproduced it after disabling Mods.

I would like to work on this as my first contribution. My proposed behavior would be:

• When assigning a shortcut that is already used by another action, show a confirmation message.
• If the user accepts, clear the shortcut from the previous action and assign it to the current one.
• If the user cancels, leave both shortcuts unchanged.

This would allow shortcuts to be reassigned without temporarily accepting duplicate bindings.

Would this approach be acceptable?

[mr-cheffy]

@EXOTARA as a prompt, for example?

[EXOTARA]

@mr-cheffy Yes, exactly, I meant a confirmation prompt/dialog.

For example:

"This shortcut is already assigned to {currentAction}. Do you want to move it to {newAction}?"

Buttons:

• Move shortcut
• Cancel

If the user chooses "Move shortcut", the old action would be cleared and the shortcut would be assigned to the current action. If the user cancels, both shortcuts would stay unchanged.

I can implement it this way if that sounds good.