kovalsky

The only solution to their genius "feature" is to uninstall the new extension and install the previous version while blocking updates. Truly brilliant.

So, I left 1Password because of the BS that came with new "features", do I have to leave Enpass in my rearview too ? That's what I've honestly been wondering after reading the "it's not a bug, but a feature" reply. The intent behind the "feature" is nice and all, I can salute the initiative, the problem is three-fold in my case: As a result of the ability to customize my keybind across my multiple browsers/operating systems, I now cannot have my preferred keybind Said preferred keybind can still trigger the configuration window where I can't set my keybind because of said improvement No reply from the developer other than on this forum and the answer is "nope, sorry, not going to happen" when clearly the wrong solution has been used to remedy an issue, therefore creating new issues. At least an acknowledgment that this should be "investigated", "looked into" or simply discussed, I would have understood that. But just a plain "nope" was kind of reminiscent of AgileBit's way of not caring about what many customers may want vs what they thought we wanted. This, coupled with another issue I read in the forum, which is a bug I've had for months now, about the double click not working on the first attempt in the browser Extension, has led me to look for another password manager, again, such a shame. Edit: I almost forgot: So, you managed to bind Command with another key ? That's funny because any combination involving Command is invalid on my Macs.