Keepassxc: Add option to not automatically clear search field

Created on 6 Apr 2019  路  15Comments  路  Source: keepassxreboot/keepassxc

The search field is automatically cleared after a few seconds minutes and there doesn't seem to be a way to disable that (that I can find anyway).

There needs to be a way to disable this behavior.

KeePassXC - Version 2.4.0

Libraries:

  • Qt 5.11.3
  • libgcrypt 1.8.4

Operating system: Fedora 29 (Workstation Edition)
CPU architecture: x86_64
Kernel: linux 5.0.5-200.fc29.x86_64

Enabled extensions:

  • Auto-Type
  • Browser Integration
  • SSH Agent
  • KeeShare (only unsigned sharing)
  • YubiKey
ux

Most helpful comment

That is your opinion, but clearly people wanted it to be auto cleared. See #2178.

I am late to the party here, just wanted to add I also don't want search to be auto-cleared.

I prefer vanilla copy/paste over maintaining browser integrations as as I use a crapload of browsers and the overhead is undesirable.

Anyway thanks @droidmonkey :D

All 15 comments

The search field clears after 5 minutes of not using the search. This timer is only active if you are not focused on the search box. This is also active when the application is minimized or sent to the tray. A few seconds is not the programmed behavior.

Please describe your use case that requires search results to remain after a long period of non-use.

A few seconds is not the programmed behavior.

That was a mistake. The title is correct though.

Please describe your use case that requires search results to remain after a long period of non-use.

While working, I use the same password throughout the day to access various network resources. Even for personal use, I'll use the same github password multiple times in a given period.

I have a similar use case to Barugon and this change in the UI has become very annoying.

I hate to be the guy to say you're using it wrong... But, you really should be relying on Auto-Type window associations and browser integration to access entries. Perhaps even better organization of your entries so that you don't have to rely on a constant search being displayed. I'll consider a setting under security to enable/disable search clearing, but the issue is highlighting an inefficiency in your workflow more than anything.

I hate to be the guy to say you're using it wrong... But, you really should be relying on Auto-Type window associations and browser integration to access entries. Perhaps even better organization of your entries so that you don't have to rely on a constant search being displayed. I'll consider a setting under security to enable/disable search clearing, but the issue is highlighting an inefficiency in your workflow more than anything.

Well, I do, when there's a browser window involved. But the specific scenario I'm dealing with is for an internally hosted Git server where I'm interfacing with it through the CLI.

Honestly, there's really no good reason to automatically clear the search field. If I want it cleared then I can click the X button instead of just clicking the search field. Anyway, it's all moot as I've moved to another solution.

That is your opinion, but clearly people wanted it to be auto cleared. See #2178.

Even the creator of that issue said it should be an option.

This is also a frustration for me, inefficient or not. :)

Thanks @droidmonkey.

Haven't got a chance to test it out yet, but thanks @droidmonkey!

i'd also like the option, the search auto resetting makes no sense to me

This was just merged to develop

In case anyone else is curious, like me, about which specific commit is being referred to above, the commit was 726dbc004d9e7e0af47eea077bf5ed19d24a8adb, in reference to issue #3400.
I'm looking forward to this feature finally getting close to release. Thanks @ziah and @droidmonkey!

That is your opinion, but clearly people wanted it to be auto cleared. See #2178.

I am late to the party here, just wanted to add I also don't want search to be auto-cleared.

I prefer vanilla copy/paste over maintaining browser integrations as as I use a crapload of browsers and the overhead is undesirable.

Anyway thanks @droidmonkey :D

Was this page helpful?
0 / 5 - 0 ratings