Accented/non-US English keys not accepted in keyboard shortcuts [investigating]

Hi Gilles and viswiz, I don't have anything to share on this at the moment, but can tell you that we're always working on localization support across a number of languages here all the time. We do recognize this is a legitimate need and are making progress in a number of areas. And when we have more to share, it'll be posted in the announcements here as well as https://releases.1password.com/.

Thanks for your understanding - we do understand that this matters!

It's really sad to see that this issue affecting everyone with a non-US keyboard layout is still not fixed after 6 months.

Hello

Have you tried to fix this ?

Is it impossible to fix with Electron ?

this problem has been submitted quite a while ago, and I do not read any fixes coming

If you are not able to fix this, please say so
Thanks

Hi @tsauer, thank you for letting us know. We know that we still have work to do on these keyboard localizations, and we appreciate you letting us know what you've seen on your setup. This is an area we will keep working to improve.

This is also broken again for me. It worked for a short while but since a while I can't use CMD+# on a German keyboard anymore. When I try to set it in the settings for "Fill in Browser" nothing happens. This is on a 2017 Macbook Pro with a Germany keyboard layout and the latest beta version (80600006) and I am pretty sure I got the same behaviour on my Windows machine yesterday (also latest beta) but I can't verify that right now.

Hi Gilles:

Thanks for the additional information here. We're investigating and continuing to make improvements here, so hopefully soon we can have this smoothed out for you!

Jack

To your questions YES, / and ù show correctly
it is a built-in keyboard MBA M1

I'm so sorry you are having issues with this Gilles. While implementing the latest change, I mistakenly applied the special character limitation too broadly. It's necessary for the time being on the lock shortcut as more work is needed before it can work reliably with special characters. I should not have applied it to the other three as those are already working even with special characters. I'll get that rectified soon but the fix will take a bit of time to propagate into beta and stable.

In the meantime, could I ask you to double check a few things for me? You mentioned that your ⌘/ key is recognized as ⌘ù, could you confirm that pressing the / in the search bar is printing that character correctly? And the same thing with pressing the ù key in the search bar? If you try to use ⌘ù as a shortcut, is the ù correctly reported? Are you using the built in keyboard or an external keyboard? If external, which one?

I suppose you cannot fix this

Now it tells me I cannot use "à" or "é" or "è" as a shortcut
but the keyboard French Canadian CSA is still not recognized as if I try "command /" it will tell me I cannot use "ù" s as shortcut ( "ù" is left of the Z key on a French Canadian CSA keyboard, not at the top left below the "esc" key

So I suppose this will never be fix with Electron

👍