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

jamesxa
jamesxa
Community Member
edited January 8 in 1Password in the Browser

I'm not sure if it's when Chrome Updates or the 1Password Extension but the "Activate the extension" keyboard shortcut keeps getting reset to Cmd+Shift+X. Since I use my browser to edit documents, this conflicts with the "strikethrough" text formatting shortcut so I'm consistently having to reset it. I've tried using a different shortcut as well as removing the shortcut to no avail. Ever since I switched to 1Password 8 and the "new" browser extension this has been happening (so for several months). This happens on all of my Chrome Profiles.


1Password Version: 8.10.7 (81007041)
Extension Version: 2.11.0, 2.12.0
OS Version: macOS 13.4
Browser: Chrome (114.0.5735.133)
Referrer: forum-search:chrome extension keyboard shortcut revert

Comments

  • Joy_1P
    Joy_1P
    1Password Alumni

    Hey @jamesxa, it is strange that the keyboard shortcut you've set for the extension in Chrome keeps changing back to the default Cmd+Shift+X. I do have custom shortcuts for the extension in Chrome on my end, and that doesn't happen to me even when the extension or browser updates.

    I'm curious, do you notice that the shortcut reverts back to its default value after an update to the extension or browser? Do you notice the same behavior occurring for your shortcuts in other extensions in Chrome? Do you clear your browsing data in Chrome regularly?

    Please let us know and we can look into this some more. We hope to hear from you again.

  • jamesxa
    jamesxa
    Community Member

    This is the only extension I have that has a keyboard shortcut assigned. Interestingly enough the "Lock the extension" shortcut I changed to nothing and it has stayed at nothing. With the latest update of Chrome and/or this extension it has gotten worse and isn't even requiring an update to reset.
    I also just discovered that clicking on the "Change on the Extensions page.." link in the 1Password Extension settings is always showing the shortcut as reset.
    Screen recording: https://photos.app.goo.gl/ih4cC5jcayYtL2tG6

    Glad this doesn't sound like a widespread issue.

    I do use Developer tools to disable caching when debugging and developing web pages but I don't typically "clear browsing data."

    I have not tried removing and reinstalling the extension yet.

  • TonyAiello
    TonyAiello
    Community Member

    This has been happening to me for about a year. It's incredibly frustrating as I, like the OP, use Google Docs and Command-Shift-X is strike-through. It's especially frustrating because it takes so many clicks to reset the shortcut (and it's really hard to find). I'd guess the reset happens about once a month, but I'm never quite sure what triggered it.

    Is there some way to just disable utterly the shortcuts? Or to change the default, so that the reset-to-default doesn't cause this behavior?

  • gaberust
    gaberust
    Community Member

    Sorry for bringing this back up, but I am also a Mac/Chrome user and have been experiencing this issue. Has anyone found a solution?

  • Hello everyone,

    Our developers have looked into the situation and have confirmed that, on certain actions such as updating the browser, Chrome can sometimes unexpectedly reset browser shortcuts.

    Since Chrome's behaviour here isn't something that we can change, I recommend reporting the issue to Chrome so that their team can investigate further: Report an issue or send feedback on Chrome - Computer - Google Chrome Help

    Hopefully this issue can be fixed in a future update to Chrome.

    -Dave

    ref: dev/core/core#21691

  • gmay
    gmay
    Community Member

    +1 for experiencing this.

    Is there something that could be added to the 1Password extension that would allow me to opt-out of 1PW Chrome shortcuts all together? (I rarely use them and the clash with Google Docs is far more disruptive than just not having them).

  • Hi @gmay 👋

    1Password in the browser provides an option to change, or remove, shortcuts through Chrome's native interface. An issue with Chrome can sometimes reset the shortcuts back to default even after you've changed them. I recommend that you report this issue to Chrome so that they can investigate this further.

    That being said, I've passed you feedback along to the team. I'm sorry for the inconvenience. Let me know if there's anything else that I can help you with in the meantime.

    -Trevor

    ref: PB-38297038

  • thavidu
    thavidu
    Community Member

    This has been bugging me forever as well, it always resets itself every few weeks no matter what I do to get rid of it. Understood that chrome reseting is not in your control, but what IS in your control is the default value- can you please get rid of it? That way users who actually want it, can set it themselves, and other, more frustrated users like me aren't more likely to uninstall the extension entirely because of it continuously taking over the google docs strikethrough shortcut every few weeks. I would argue that the userbase of google docs is likely larger than the number of people who use the keyboard shortcut feature for 1password, so I suspect your retention opp-size of making this change (and giving up the default) is definitely worth it.
    Alternatively, just set a different default keyboard shortcut that doesn't conflict with the google doc ones ><

    Its also really rare for any extension to even bother setting a default shortcut key-- I have 20 chrome extensions installed and only about 3 of them install themselves with a default shortcut key.

  • @thavidu

    I'm sorry for the frustration. As you noted, the shortcut resetting itself is a bug in Chrome and it isn't something that we can fix on our end. I encourage you to report the issue to the Chrome team: Report an issue or send feedback on Chrome - Computer - Google Chrome Help

    Regarding changing the default shortcut, or turning off all shortcuts entirely, I've passed your request and feedback along to the team so that they can consider such options for the future. 🙂

    -Dave

    ref: dev/core/core#8796
    ref: dev/core/core#21691
    ref: PB-39583259

  • amplest
    amplest
    Community Member

    @Dave_1P: It seems like you're not really listening to what @thavidu is saying. Even if the bug is in Chrome as you say, there is a simple solution for 1Password: Don't use a standard Google Workspace shortcut as your default.

    Google Workspace has 3 billion users, including 6 million paying business customers. Wouldn't 1Password like a bigger piece of that action? Why make your software incompatible with it by default?

  • Dave_1P
    edited August 2

    @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

  • amplest
    amplest
    Community Member

    @Dave_1P 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

    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

  • agram
    agram
    Community Member

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

  • @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