MagicKeyboard: Added key to insert old password #1074
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a key to ease the process of changing a password, by retrieving the previous password from an entry's history.
There are many reasons wanting to change a password even when using a password manager, for example, for expired passwords, known breaches or changing to a safer password after migrating to KeePassDX.
It's not clear or intuitive how to change change a password when using the MagicKeyboard on websites that require entering your previous valid password. This change introduces a key to retrieve an entry's old password for a streamlined procedure:
This process is resilient to errors, if the process timeouts or the password is rejected, the old password is still stored in the database. If the new password is rejected, the user can change it on the main app, save it, delete the last history entry (with the rejected password) and repeat.
I am not sure whether adding an extra key is your preferred way for this. After all, this feature is not used so often and having an additional key should be justified. Maybe it would be better as an entry of the "custom fields" menu? I am not sure what you would prefer (or even if this is acceptable on your vision for the app), so I appreciate your feedback.