Design language

MrC fair enough that there’s people who don’t actually care about a Mac-assed app experience. However, the change from ⌘0 meaning "all (filtered) vaults" to "reset zoom" is jarring and should have been seen as a problem well before it was implemented. There are two types of apps where I expect to find zoom bindings and will accept ⌘0 as "reset zoom":

1. Web Browsers (wholeheartedly)
2. Editors (grudgingly)

You know who else implements this bonkers behaviour? Slack. It’s a constant low-level reminder that the people at Slack don’t actually care about the user experience of the people who use their products, because people don’t change the zoom on their chat interfaces frequently if ever. It’s a reminder to people that a Mac-assed experience isn’t even a consideration, much less respect for conventions of differing platforms. (It’s also a constant reminder that, IMO, Slack is a perfect fit for Salesforce because neither company actually gives a damn.)

Mac apps often (but not always) treat ⌘0 as "show the main window". Especially if, like with 1Password, there’s only one window. 1Password used to treat it as "show the All Vaults view". Now it’s "reset zoom". It’s wrong on three counts:

• it no longer feels like 1Password did (and therefore feels like a change for change sake, or because of laziness),
• it no longer feels like a Mac app (and emphasizes the foreign unnatural behaviour of Electron apps)
• it is almost never what the user of the application wants, especially if they’ve gone to the trouble of reducing zoom to, say, 80% in the preferences menu.

Accidental keypresses of bindings that previously meant something else or should mean something else on the platform are simply wrong.