Summary

It's fairly common for me to mistype my master password when unlocking my database. When I do this, I prefer to just retype the whole password again from scratch as it's more a muscle memory thing rather than actual memory. In order to do that, though, I have to press Ctrl-A to select the entire password field. This works, but it's an extra step.

I'm running version 2.4.3 on Centos 7. I searched the bug database for a similar issue, but didn't find it. Feel free to let me know if this is already implemented in some way.

Desired Behavior

After typing a password on a master key and attempting to decrypt the database, if the database fails encryption, show the message that says "Error while reading the database: Invalid credentials were provided..." and then select the entire password field so that the user can begin typing their password again to attempt a new unlock.

Possible Solution

If this isn't a desired default feature, it could be added but controlled via a setting in the Settings panel. Something like "After incorrect master password entered, auto-select password field to allow new entry". Or even "After incorrect master password entered, clear password field"

Context

Discussed in Summary