Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Auto-Type when using AutoOpen #4432

Closed
tyllmoritz opened this issue Mar 12, 2020 · 2 comments
Closed

Improve Auto-Type when using AutoOpen #4432

tyllmoritz opened this issue Mar 12, 2020 · 2 comments

Comments

@tyllmoritz
Copy link

tyllmoritz commented Mar 12, 2020

Summary

When using Auto-Type I am asked to unlock the Database in the currently active tab.
I have a Main-Database (with folder AutoOpen) and a Child-Database (which is opened automatically). I do not know the Child-Databases password.
When the current Tab is the Child-Database, I have to switch to the Main-Database first.
When the current Tab is the Main-Database, KeePassXC first tells me, that the Entry was not found, then opens the Child-Database. Using Auto-Type again succeeds.
KeePassXC_AutoOpen_and_Autotype

Desired Behavior

  1. For Databases, which were opened using Auto-Open, ask for the Password of the Main-Database instead.
  2. Open all Child-Databases before searching for Auto-Type-Entries.

Possible Solution

  1. when locking Databases, which were opened with AutoOpen, switch the active Tab to the Main-Database.
  2. Wait with AutoType until after AutoOpen finished

Partial Solution 2

#2322, Case 2 would help a with manually switching to the Main-Database.

@tyllmoritz
Copy link
Author

tested on Version 2.5.1, AppImage, CentOS7
#3728 (comment)

I think it's still the same on 2.5.3.

@droidmonkey
Copy link
Member

droidmonkey commented Mar 12, 2020

This will be solved with #2322 no need for a duplicate issue. We don't make a distinction in a database that was opened with auto open. We probably could, but there really is no need. The referenced issue will clear up the ux challenges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants