Forum Discussion

johyphenel's avatar
johyphenel
New Contributor
2 years ago

Manually setting Chrome extension shortcut gets overridden

Like many others, I like to use cmd+shift+x for "strikethrough" on Google docs. To change it I go to chrome://extensions/shortcuts and change 1Password "Activate the extension" to cmd+ctrl+shift+x.

The problem is, I find myself doing this every few weeks (or maybe every month? I haven't kept exact track)... Something in 1Password keeps reverting the shortcut to the default, it's really frustrating!!

I think I've done this 4-5 times this year.


1Password Version: Mac 8.10.33
Extension Version: 2.25.1
OS Version: MacOS 14.5
Browser: Chrome 126.0.6478.114

6 Replies

Replies have been turned off for this discussion
  • johyphenel

    Thank you for the feedback, I've passed your request along to the team internally.

    -Dave

    ref: dev/core/core#8796

  • johyphenel's avatar
    johyphenel
    New Contributor

    You could change your default shortcut not to conflict with Google Docs/Sheets...

  • johyphenel

    Thank you for the reply. Based on our developer's investigation, it looks like Chrome will sometimes reset browser extension shortcuts on certain actions such as updating the browser.

    Because the bug exists in Chrome itself, this isn't something that 1Password can change. I recommend reporting the issue to Chrome so that their team can investigate further and develop a fix: Report an issue or send feedback on Chrome - Computer - Google Chrome Help

    I'm sorry that I don't have a better answer at this time.

    -Dave

  • johyphenel's avatar
    johyphenel
    New Contributor

    I don't think I've had this issue with other extensions in the past, but I haven't had to change any other extension shortcuts in long while.

    This is not the beta extension

  • johyphenel

    Do you notice the same behavior occurring for your shortcuts in other extensions in Chrome? Do you clear your browsing data in Chrome regularly? I'm a little outside of my area on this one, but if memory serves me correct it is the fourth character causing you trouble. As a test could you try using a only 3 characters for the shortcut and let me know if you experience the same issue?

    ref: dev/core/core#21691