You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, I tried searching and reviewed the pinned issues
Brief Summary
While viewing the database settings and the app settings, I pressed the gear (cog) settings button a few times which toggled between the two settings windows. If I was last on the app settings and I cancelled the screen from the lower right 'Cancel' button, it would go back to the DB settings, but the text and button menus would become unavailable (disabled) to some extent. I would have to click the gear another time to re-open the app settings and cancel again and this would make the menu active once again. With the combination of moving between the DB settings and the app (which disables the menus), by clicking the gear settings button, this puts the menu is an odd state.
CAUSE: By opening the App settings, this is what throws the menu into a semi-disabled state, but by opening the DB settings before opening App Settings, it locks the menu into a semi-disabled state until you re-open and close the app settings for a subsequent time.
Have you searched for an existing issue?
Brief Summary
While viewing the database settings and the app settings, I pressed the gear (cog) settings button a few times which toggled between the two settings windows. If I was last on the app settings and I cancelled the screen from the lower right 'Cancel' button, it would go back to the DB settings, but the text and button menus would become unavailable (disabled) to some extent. I would have to click the gear another time to re-open the app settings and cancel again and this would make the menu active once again. With the combination of moving between the DB settings and the app (which disables the menus), by clicking the gear settings button, this puts the menu is an odd state.
CAUSE: By opening the App settings, this is what throws the menu into a semi-disabled state, but by opening the DB settings before opening App Settings, it locks the menu into a semi-disabled state until you re-open and close the app settings for a subsequent time.
Steps to Reproduce
To Break
Menu becomes semi-disabled <<< HERE IS WHERE THE INTERFACE BREAKS/MISBEHAVES
To Fix: Open and close app settings once more
Menu becomes available once again
Expected Versus Actual Behavior
Expected: When exiting any settings, the menu should become available.
Actual: See above
KeePassXC Debug Information
Operating System
Windows
Linux Desktop Environment
None
Linux Windowing System
None
The text was updated successfully, but these errors were encountered: