Feature request: Optional Autosave similar to Classic browser extension (prompt after logging in)
Currently there is awesome feature in desktop+classic extension which shows you prompt to create new or update existing login AFTER logging in. Very similar to most browsers in-built password managers.
For example, I don't have my Instagram credentials stored in 1Password yet. When I go to instagram.com and login, this little windows pops ups and I can save credentials to 1Password with one click (or if I put wrong credentials and login was not succesful, I can click "Not now" and try again):
Same window pops up if I login with other than already saved credentials but instead it asks me to update existing record. For example, I imported my Facebook credentials from browsers in-built password manager to 1Password but credentials would not work (I had changed password but not updated it to browsers in-built manager). After logging in with correct credentials, I can update 1Password entry with one click:
How 1Password X differs from this is you have to 1) manually bring the pop-up by clicking "Save in 1Password" 2) do it before logging in.
1)
2)
So there are already similar popups in 1Password X but they don't show up automatically.
Here comes my feature requests: add option to enable Autosave.
Enabling this would show "Save in 1Password" pop-ups after logging in using other than already stored credentials.
My other feature request would be autofill (automatically offer to fill already saved credentials) in desktop+classic extension but I guess classic extension won't get new features and 1Password X is heavily recommended over classic extension. Because autosave is in desktop+classic extension and autofill is in 1Password X, I have installed and used both browser extensions simultaneously. This setup is not recommended but so far I have had no issues with it.
1Password Version: Desktop 7.6.791 and X 1.23.1
Extension Version: 4.7.5.90
OS Version: Windows 10
Sync Type: Not Provided
Comments
-
Thanks so much for your feedback, @liimasim! I really appreciate you taking the time to share it with me. I've passed your thoughts along to my team as well.
In case you're curious why 1Password in the browser behaves this way, you can check out one of my previous explanations here. If that sparks any other questions, please don't hesitate to send them my way. :chuffed:
ref: dev/core/core#634
0