What Enpass should do instead, is to check system keyboard bingings in Firefox (and other browsers) since in macOS at least you can alter every possible keyboard shortcut to be something else. ![]() What bothers me with this behaviour is that Enpass has made it so that Firefox (or any other browser) default keyboard shortcuts are not permitted anymore to be used as a Enpass keyboard shortcut and these settings are hardcoded to new version of Enpass Extension. What I didn't do was make any personal attacks by saying things like " I couldn't possibly give less of a shit," and "wacko leftist crap," and "are you 5?" - none of which have anything to address the actual problem at hand.įor the sake everyone else here - and the actual subject of this thread - I'm done with this conversation. I said I understood why they made the change (which is not defending the decision, just acknowledging the reason they did it), and I very much criticized their handling of the rollout (suggesting how it could have been handled better), and I criticized their tone-deaf handling of the backlash (in the very next post after your criticism of the same). What did they think would happen when, without explanation, an update broke a common keyboard shortcut?Īre you kidding me? You're trying to defend developers changing the PRIMARY WAY people trigger their application every day, multiple times per day, with zero notice and then not allowing people to set the actual setting back to our preferred method of triggering the application again with zero notice and then responding to user's justifiable anger with "it's a new feature, and not a bug"? And that's ok?!?! You're really trying to defend that? Are you 5? How Enpass couldn't not have seen this coming is hard to imagine. The fact that Enpass did not do this has led to all this confusion, and the assumption by users that this "feature" is a bug. Click here to create your Enpass shortcuts." With the "click" sentence linking to the browser's settings/shortcuts page. It would have been a simple matter - and 1000% more user-friendly - to include a sentence on the "Enpass browser extension has been updated" tab that reads, "To make Enpass more compatible with the way most browsers handle keyboard shortcuts, users need to create their own new keyboard shortcuts for displaying Enpass and autofilling account information for this updated Enpass extension. (Perhaps an easy matter for developers and techies, but not for the average Joe Websurfer.) My point about that phrase was that saying "it's not a bug, it's a feature" sincerely indicates that a) the developers aren't understanding the problem, b) the developers aren't taking users' concerns seriously, and c) the developers are apparently unaware of the history of that phrase and how dismissive it reads.īut the bigger problem remains that the developers didn't bother to explain this change at all. They apparently just expected users to discover their keyboard shortcuts don't work anymore, and then expected users to find their way to the shortcut settings, then set up their own new shortcuts. Saying "it's not a bug, it's a feature" is when software developers UNINTENTIONALLY create a error in the software, and try to pass it off as a new feature.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |