When using the desktop app on any OS that requires a keyboard (Windows, MAC, Linux), the app should automatically start the search when a key stroke is detected. This would make it easier for those of us that use the app everyday, without using browser extensions.
I would recommend this as a toggle in the settings so this new behavior is opt-in for “power” users.
Thank you in advance for your consideration of this feature request.
Could you please clarify whether you are proposing that search results be shown based on only the first entered characters (as opposed to the current behavior, in which searching only starts after at least 2 characters have been entered, to improve performance), or just that the search box be focused whenever a key is pressed?
If the latter, do you wish this focusing of the search bar to occur only when pressing keys that correspond to printable characters, or also when detecting keystrokes associated with control characters such as Tab, Alt, ←, →, etc. (used for keyboard navigation)?
The second one. I’m proposing a “power user” setting where a keystroke (when not already in a text field) triggers and focuses the search box. I know it’s just one click to get to the search box, but I think this opt-in feature will add a nice usability function to the desktop app.
Edit to add: Use case = open app → start typing → find what you need
Correct, the keystroke values will need to be considered, and yes, it should not be active in edit mode. I didn’t say it was going to be an easy feature, just a useful one for quick search.
Not an unreasonable request, but perhaps it needs to be a separate feature request thread. FYI, you are supposed to be able to focus the Search bar using Ctrl+F, but this feature is currently broken.
You might also want to consider using the browser extension instead of (or in addition to) to the Desktop app, as the extension does open with the search bar focused.
Just FYI, feature requests are discussed here on the forum, but bugs have to be reported on GitHub. (in the “issues” section of the corresponding repositories)