Ensure no duplicate shortcut keys for context menu items

[Aelius]

When you right-click something, you can press a key to select an item from the context menu without having to click anything. In the example below, you can press "C" to copy the link address.

The problem is, in Vivaldi, certain shortcut keys are the same for multiple menu items. For example, suppose I right-click something that I think is a copyable link and I press "C", expecting it to copy the link. However, suppose it wasn't actually a copyable link. This might happen:

Here I would expect C to copy a link to the tweet I right-clicked, but it instead selects "Cast".

This is bad UX. If there are no available letters for a shortcut (e.g., the other three letters in "Cast" are already used), free up one of the other letters elsewhere, or change the name from "Cast" to something else.

I'm aware that this can be worked around by removing certain items from the context menu via Vivaldi's settings (Appearance->Menu). But first of all, duplicates should not happen as a matter of principle and prudence (how many people are savvy enough to figure out this workaround?). And second, sometimes the user might want both items (e.g., Cast and Copy Link Address).

[Pesala]

@Aelius I understand where you're coming from, but the access keys are set automatically. Renaming "Cast" to something else might work for English, but there are dozens of UI Languages for Vivaldi. Inevitably, there are going to be conflicts in some languages.

The access keys also change for Developers Tools on the page context menu, but Developers Tools on the link context menu. Ideally, they would be D for both, but on the link context menu D is already used for Add Link to Web Panel.

Going through each permutation on every menu to ensure there are no conflicts is impractical, and is clearly not going to happen. Customising the menu for yourself is surely the only way to go here.

[Aelius]

@Pesala Ah, I didn't know they were set automatically. It makes sense, and you're right that that means it would be basically impossible to ensure there are no conflicts. Thanks for the explanation!

[LonM]

@Aelius I marked this as "will not do", as this is something that is controlled by the chrome code and mostly happens automatically, so there's not much vivaldi can do to change.