Skip to main content
December 31, 2021
Question

Keyboard Shortcuts For Safari Extension?

  • December 31, 2021
  • 73 replies
  • 4328 views

The keyboard shortcuts for the Safari browser extension still use the old 1Password X ones--e.g., "Cmd + Shift + X" to show 1Password in Safari, and "Cmd + Shift + L" to lock 1Password. Can we customize these just like in the other browsers? Or at least mirror the custom shortcuts we have in the desktop app?

Also, the keyboard shortcut I set up for locking the 1P 8 Early Access app doesn't work anymore. I tried changing it, etc. When I'm on the Mac desktop, for example, the system reads my keyboard shortcut just as if I had pressed any letter. (For example, if you're on the Mac desktop screen and press a letter on your keyboard, it will select the first file/folder on the desktop that corresponds to the letter. In other words, there's some kind of bug that's causing the Mac to not send the command to lock the 1Password app. It over-rides it?)


1Password Version: Early Access 8.5
Extension Version: latest for Safari; 2.x.x
OS Version: macOS 12.1.x

73 replies

December 3, 2022

Please allow users to customize these as they conflict with other shortcuts.

December 8, 2022

@k3liutZu you can customize the shortcuts in the 1Password desktop app and extensions settings in all browsers except for Safari. In Safari specifically, there is a limitation which prevents us from allowing this shortcut to be customized or removed. We have an internal issue open about this, and our developers are looking into how we can make some improvements in a future update to 1Password, along with our friends at Apple. I apologize for any interruption in your workflow caused by this.

December 8, 2022

Thank you for the reply @Joy_1P

I guess I'll try using Chrome when I want to use Google Sheets with that specific shortcut for now.

December 9, 2022

@k3liutZu I appreciate your patience and understanding. I'm sorry that there's not a better workaround, but I do hope that using Google Sheets in Chrome can help for now.

December 30, 2022

AUGH! Same problem here. PLEASE do what you can to allow customization of the Safari shortcut. Thanks

January 6, 2023

Same problem! Can one just turn off the shortcut?

January 9, 2023

Update on Safari extension allowing users to disable the keyboard shortcut to open 1Password?

February 12, 2023

+1M vote for taking this thorn out of 1P customers who use Safari, Google Docs, and the Strike-Through shortcut key Cmd-Shift-X.

I use Strike-Through about 1000x as often as I manually open 1P. Most often, 1P opens when I need it. Thank you Agile Bits Product/Engineering for getting that part right. But, Cmd-Shift-X as a shortcut for Strike-Through has been around a long time. The notion that when integrated with Safari 1P should take-over Cmd-Shift-X and thereby force the customer to go without a shortcut for Strike-Through is very much getting Product/Engineering wrong.

I'm not raising a feature request. This is a bug. It's an obvious product spec oversight to usurp a well-know and commonly used key sequence which then breaks other functionality. At a minimum, there should be an option to completely disable the shortcut key to open 1P. (Personally, I had never opened 1P manually with a shortcut prior to this issue surfacing. On the rare occasion 1P doesn't open when I need it to, I normally Alt-Tab to the full app to create/update an entry. I prefer the full UI for those types of updates anyways.)

I chose 1Password because it is very intuitive and reliable. But this bug is devastating for my productivity in Google Docs. So I either need to install a different browser (acceptable on some systems, not this one) or uninstall 1P for Safari extension (at which point 1P will never open when I want it to.) Sorry to say it, but taking over Cmd-Shift-X without permission or recourse is a straight up fail.

Please fix this.

Thank you,

-J

steph_giles
1Password Employee
February 14, 2023

@jjsurfer7

I'm sorry for the delay in getting back to you, although I do not have an update at this time I have added your voice internally.

@jschalfant

Thank you for taking the time to provide this detail. I agree with your feedback and have passed it on to the team.

I apologise for the inconvenience this is causing you.

ref: dev/core/core#8796

February 20, 2023

Hello @steph.giles.

Thank you for hearing me and passing along my concern to development, along with your endorsement. I understand software changes can take some time to make it through the queue. On the other hand, because it's fairly described a bug and not a feature request, I do expect it should receive some priority in the queue.

Might you be able to provide monthly updates on this thread regarding the progress of the fix?

Thank you again!

-J