Cmd + Backquote open quick access even if shortcut is map to an other key combination
Hello, I am using 1Password for years but since v8 i'm having an anoying problem with keymap.
The quick access window always open when i'am using key combination CMD + BACKQUOTE.
I don't know if this is a reason of the bug but, I'am french and i'am using an azerty keyboard.
I've tried with a fresh macos install but the problem is persistant, so not related with my macos config.
Did some one have the same problem ? Or can support team take a look to this issue ?
Best Regards
1Password Version: 8.9.10
Extension Version: Not Provided
OS Version: 12.6
Browser:_ Not Provided
Comments
-
Hi there @jbournonville
All four of the keyboard shortcuts you see in 1Password's Settings are global shortcuts, meaning they'll work anywhere in macOS, not just in 1Password. If you're finding that another app uses one of them for its own functions, you can change 1Password's shortcut to something else.
For example, in some apps I use, ⌘\ (Command–Backslash) is used to show or hide the sidebar, so I've changed it to ⇧⌘\ (Shift–Command–Backslash) in 1Password's Settings so it doesn't collide.
Give that a try and let me know how you get on. I'll be here if you need further help. :)
— Grey
0 -
Hello,
I've got the same issue here:
- MacOS BigSur 11.7
- french layout keyboard (AZERTY mac)
The Command + Backtick (`) is bound in OS system preferences to cycle through all windows of the same application
The Shortcut in 1Password to open Quick Access is Command + Shift + SpaceWhat's happen: Both shortcuts open the quick access
Expected behaviour: Cmd + ` should switch to next window of the current app having focus, Cmd + Shift + Space should open 1Password Quick AccessI'm started using 1Password 5 for Mac, then migrates to 8 now.
It's really annoying for me, as I use Cmd + ` a lot to cycle through application's windows.
What I already tried:
- redefined the shortcut in system preference: impossible, the shortcut can only be enable or disable
- tried to disable then enable again the shortcut in system preference: change nothing to the situation
- tried to change the shortcut in 1Password settings: it works to change the Quick Access shortcut, but Cmd + ` still bound to Quick Access.
Hope it helps to better understand the issue. And therefor to solve it.
Regards
0 -
You mentioned:
redefined the shortcut in system preference: impossible, the shortcut can only be enable or disable
You can change the "Move focus to next window" shortcut for macOS. (I've done this because I'm on a UK keyboard and Command-Backtick is a little bit fiddly for me.) Here's what to do:
- In System Preferences, open the Keyboard pane, and choose the Shortcuts tab.
- Click "Keyboard" in the sidebar, then double-click where it says ⌘` next to "Move focus to new window", like this:
You can then set a new keyboard shortcut. Once you've done that, you should be able to change the "Show Quick Access" shortcut in 1Password's Settings.
Give that a try and let me know how you get on.
0 -
Hi @GreyM1P
Sorry for my (very) late answer (I know it doesn't help you to help me …)
Here is my configuration as of today, still not working:- MacOS 11.7.4 on 15" mid-2014 MacBook Pro
- System Preferences configured to cycle through windows with CMD + `
- 1Password Settings configured to open Quick Access with CMD + Shift + Space
Unfortunately, when I use CMD + `, it opens 1Password Quick Access instead of cycling all windows of the focused application.
When I quit 1Password, CMD + backquote works as expected, but I can't access my password vault anymore obviously 😕Following some screenshots:
I also tried to uninstall 1Password following this procedure https://support.1password.com/uninstall-1password/ and reinstall the latest version but the issue is still there
Hope it will help
0 -
Thank you for the reply. Have you tried Grey's suggestion to change the "Move focus to next window" shortcut for macOS? Here are the steps again:
You can change the "Move focus to next window" shortcut for macOS. (I've done this because I'm on a UK keyboard and Command-Backtick is a little bit fiddly for me.) Here's what to do:
- In System Preferences, open the Keyboard pane, and choose the Shortcuts tab.
- Click "Keyboard" in the sidebar, then double-click where it says ⌘` next to "Move focus to new window", like this:
You can then set a new keyboard shortcut. Once you've done that, you should be able to change the "Show Quick Access" shortcut in 1Password's Settings.
-Dave
0 -
Guys, this is a terrible answer and you need to do something about this! Are we really supposed to change our ways on such a central shortcut just because you are not going to make the effort to remove a behavior that is unexpected and undocumented? We should have a way to opt out from this, instead of changing a system-wide shortcut...
0 -
I'm sorry that you're also running into the issue. The suggestions that Grey posted are meant to help while our developers look into this further, I'm sorry that this wasn't clear. Everyone's reports have been added to the internal work item open for the issue.
Can you tell me what kind of keyboard layout you're using on your Mac so that I can pass that information along to the team? 🙂
-Dave
ref: dev/core/core#20365
ref: dev/core/core#151740 -
Hi @Dave_1P,
My keyboard layout if ISO/french according to this doc: https://support.apple.com/en-us/HT201794
It looks similar to this one (credits to Apple):
https://store.storeimages.cdn-apple.com/4982/as-images.apple.com/is/MK2A3F?wid=2000&hei=2000&fmt=jpegI'm now using the 8.10.12 release of 1Password with still the same issue.
Changing the shortcut for 'Move focus to next window' from the System Settings panel works as expected: the new shortcut make the focus moving to the next application window.
Hope it helps.
Regards,
Guillaume0 -
Hello,
I just registered to inform you the same problem is happening on Czech keyboard (cmd+¨) and latest version of 1password and OSX on M3 mac.
At first I thought there was an error on my side but you somehow have hardcoded this shortcut and I simply don't understand how such a trivial issue is still not fixed after 5 months.
Please do something about it.
Thank you.
0