-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Order of context menu options #2813
Comments
The context menu re-uses the main menu for entries. I do agree it does not make much sense to make a new entry when you are interacting with an existing entry. We should offer a different menu for the context menu or remove "New Entry" when interacting with a specific entry. |
please see my recommendation for how context menu should be ordered for existing entries (with potentially removing "New Entry", as mentioned here): |
* Fixes #2813 Added special context menu for entries to move the most-used actions to the top. Re-ordered actions in the entry menu to be more user friendly.
* Fixes #2813 Added special context menu for entries to move the most-used actions to the top. Re-ordered actions in the entry menu to be more user friendly.
* Fixes #2813 Added special context menu for entries to move the most-used actions to the top. Re-ordered actions in the entry menu to be more user friendly.
* Fixes #2813 Added special context menu for entries to move the most-used actions to the top. Re-ordered actions in the entry menu to be more user friendly.
* Fixes keepassxreboot#2813 Added special context menu for entries to move the most-used actions to the top. Re-ordered actions in the entry menu to be more user friendly.
KeePassXC 2.4.0 for Windows has changed the order of the context menu options. Instead of having the most used options at the top (
Copy username
andpassword
), now it hasNew Entry
, even when you're clicking on an existing entry.Please consider placing those two options at the top again or letting us customize the order.
The text was updated successfully, but these errors were encountered: