Shortcut takes over

This was quite annoying. The workaround needs to be very public with the installation instructions.

This still doesn't work on a mac w/ the safari 1p extension running. Cmd-shift-x opens the 1password extension still and won't do strikethrough in google docs.

Just wanted to shout out thanks again for the variety of solutions proposed. In 2022, I fixed the issue using Mac preferences. The problem just started to reoccur again a couple weeks ago. Nothing changed on the mac side, so changed the 'open' preference in the browser app preferences to something else and now my strike through works again.

I don't understand...this doesn't work with safari still as far as I can tell. Does it? If so please tell me how.

+1, I'm a professional writer working almost exclusively in google docs. This is so disruptive to my workflow that I would happily migrate to an entirely different password manager or disable the browser extension if my IT team would let me. Please at least give me the option to customize the shortcut on the 1P side.

Thank you folks. I've passed on your thoughts to the team.

ref: dev/core/core#8796

Changing the Keyboard shortcut for the browser extension works for a period of time and then eventually, inevitably switches back to Command-Shift X. Approximately once every three weeks or so. Please, let me remove the keyboard shortcut entirely and permanently, I never want this to pop up, especially when using Google Docs.

Hey @saro, it's strange that the keyboard shortcut switches back to Command-Shift-X. I've never encountered the keyboard shortcuts changing without making updates to them myself.

What browser are you using? Do you clear your browsing data on a regular basis? Do you notice any other changes in your extension settings when the keyboard shortcut switches back?

Hello, I am using Chrome on macOS. I do not notice any other changes in my extension settings.

Thanks for getting back to us @saro.

Do you notice anything else happen when it switches back? Are you clearing your browsing data? Is this happening after an update or does it just seem sporadic?

It would be good if we could pinpoint exactly when this is happening so we can file an issue with our team to see if we can improve the behaviour in certain scenarios.