Why does the Chrome keyboard shortcut keep reverting/resetting to its original value?

Jeff-POI​ and lambdamusic​ 

Thank you for following up and I'm sorry that you continue to be affected by the issue. We don’t have plans to change the default shortcut at this time, as many of our customers rely on it as part of their daily workflows. Instead, we’re instead making use of Chrome’s built-in keyboard shortcut management. This lets you customize the shortcut if the default one conflicts with another extension or website.

The team and I still haven't been able to reproduce the behaviour that's been reported by a small number of Chrome users where Chrome will reset chosen keyboard shortcuts after an update. Would you be able to take a screen recording of the following the next time there's an available Chrome update: 

1. Show that you've changed your keyboard shortcut from the default to something else.
2. Update Chrome. 
3. Show that the shortcut has changed. 

You can find instructions on how to create a screen recording here: 

• How to record the screen on Mac
• How to record your screen on Windows

A screen recording will allow us to better investigate and reproduce the issue on our end. Once the screen recording is created, please send an email to support@1Password.com and include a link to this thread. After emailing in, you'll receive a reply from BitBot, our friendly robot assistant with a Support ID that looks something like [#ABC-12345-678]. Post that here, and I'll be able to locate your message and send you a secure upload link for the screen recording.

-Dave

Issue=PA-522

Just echoing Jeff-POI​ comment, is there any update on this issue? 

Seemingly it's affecting a lot of uses and changing the default shortcut isn't such a big deal. 

1P_Dave​ Has there been any movement on this, or simply changing the shortcut from one that is so useful already taken by a larger more commonly used web program/browser? The 1P extension is incredibly helpful but every time the keyboard shortcut resets I get closer to simply deleting the extension all-together. 

My extension also resets every single time there is an update to the extension or to chrome. It's untenable.

uhuhleuh​ and lambdamusic​ 

I'm sorry that you're both still running into the issue. It's not entirely clear why keyboard shortcuts are being reset for certain users but our development team believes that this is a Chrome issue since we see reports online for users of other extensions as well. 

Since we still haven't reproduced the behaviour on our end, can you tell me the following: 

1. How often do your shortcuts reset? Every day? Every week? Every month?
2. Do your shortcuts reset after an update to the 1Password extension? Or after an update to Chrome itself? 
3. Do you use any other extensions that allow you to configure shortcuts and do those reset as well? 

I look forward to hearing from you.

-Dave

#21691

Hi there,

It seems like after 4 years, this issue continues to exist: I repeatedly delete all 1Password Chrome extension's shortcuts, just to have the extension add Command-Shift X. Any change you can fix this soon?

MacOS: 15.4.1 (24E263)
Chrome version: Version 136.0.7103.48 (Official Build) (arm64)
1Password extension: 1Password Nightly – Password Manager 8.10.78.7

Thanks

agram

I'm sorry for the frustration. I don't have any updates to share at the moment, our developers have reported the issue to the Chrome team and I encourage you to submit a report as well: Report an issue or send feedback on Chrome - Computer - Google Chrome Help

-Dave

Any updates here? As the others above have said, it would be great for 1Password's product team to add this functionality. Incredibly frustrating...

amplest

Thank you for sharing your perspective and feedback. Our development team has reached out to our friends at Chrome and hopefully this is an issue that can be fixed in the future. In the meantime, I've shared your request that the default shortcut be changed with the appropriate team for their consideration. 🙂

-Dave

1P_Dave I grant you that not everyone uses Google Workspace strikethrough on a regular basis. On the other hand, I've been a 1Password customer since version 3 (i.e. for at least 10 years) and I don't think I've used 1Password's Command-Shift-X shortcut once in that time. At least not intentionally!

I understand your argument about being reluctant to change some existing users' workflows. It might hold a little more weight for me personally if 1Password 8 hadn't completely removed critical functionality that I used every day in the previous five versions. But I do understand it.

Anyway, my point isn't to sound churlish. It seems that 1Password has made the decision to deemphasize its roots as being the most seamlessly integrated password manager for individuals and focusing more on enterprise functionality. That honestly seems like the right strategy, even if it means hobbling the consumer product. Given that enterprise focus, I'd consider evaluating the conflicts with Google Workspace as to how it aligns with that strategy.

Obviously, conflicting with strikethrough is not going to make or break the case for an enterprise deployment. But there are a lot of enterprise solutions, including free ones, and I think 1Password's best selling point would be its integration.

Anyway, something to think about.

amplest

I know how disruptive this issue can be and Google Docs is indeed a very popular service. However, not all 1Password users also use Google Docs (or use strikethrough with regularity) and changing the default shortcut is a big decision since it will disrupt the workflow of everyone who has been using that keyboard shortcut for years to open or close the 1Password pop-up.

The reality is that there are many websites out there that feature conflicting shortcuts with 1Password and, because of these potential conflicts, 1Password's browser extension supports the ability to change the default shortcut in all browsers that allow us to include this functionality including Chrome, Edge, Brave, and Firefox. A bug in Chrome can sometimes reset a user's chosen shortcut for a browser extension and hopefully that is fixed by the Chrome team in the future. I recommend that you report the issue to Chrome so that they're aware of the impact to you.

Although I'm not the one who makes the decision on whether to change the default shortcut, or implement other solutions, I'll continue to make sure that this is in front of the relevant teams and voice everyone's feedback internally. The experience here can definitely be improved and I hope that a solution that works for all users can be found.

-Dave

ref: PB-41224611