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

Search field no longer has focus when db is opened #10530

Closed
SerpicoSal opened this issue Apr 1, 2024 · 2 comments
Closed

Search field no longer has focus when db is opened #10530

SerpicoSal opened this issue Apr 1, 2024 · 2 comments
Labels

Comments

@SerpicoSal
Copy link

Overview

version 2.7.7 on linux (ubuntu 23.10 mantic) longer defaults keyboard focus to the "Search" text box after opening a DB.

Steps to Reproduce

  1. Select a DB to open
  2. Enter password
  3. Type in search value (e.g. "t:github")

Expected Behavior

In KeePassXC v2.7.6 and older, after entering the correct password, the search field was immediately given focus which permitted a faster entry lookup.

Actual Behavior

After successfully opening a db, no UI elements in KeePassXC have focus for keyboard interaction.
Pressing ctrl+F however works correctly to put the Search UI box in focus, it just is no longer the default behavior.

Context

This is a NIT issue with a reasonable workaround. I just need to retrain my instincts to press ctrl+F after my DB has been unlocked.
I'm only reporting this issue as it was a noticeable change in v2.7.7 and may have been for a good reason that I'm unaware of.

KeePassXC - Version 2.7.7
Revision: 68e2dd8

Qt 5.15.10
Debugging mode is disabled.

Operating system: Ubuntu 23.10
CPU architecture: x86_64
Kernel: linux 6.5.0-25-generic

Enabled extensions:

  • Auto-Type
  • Browser Integration
  • Passkeys
  • SSH Agent
  • KeeShare
  • YubiKey
  • Secret Service Integration

Cryptographic libraries:

  • Botan 2.19.3

Operating System: Linux
Desktop Env: KDE Plasma 5
Windowing System: X11

@SerpicoSal SerpicoSal added the bug label Apr 1, 2024
@droidmonkey
Copy link
Member

..... #10459

@SerpicoSal
Copy link
Author

Thanks @droidmonkey, sorry that I didn't spot the duplicate issue before reporting.

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

No branches or pull requests

2 participants