Skip to content

UX regression: keyboard disappears during search after a very short interval #866

@climategadgets

Description

@climategadgets

Action Taken

Entering the search term, pause momentarily to hunt for the next key

Expected Behavior

Entered text stays, keyboard stays, all the way until the search activation button is tapped

Actual Behavior

After a very short timeout, the keyboard disappears and the search is executed. This disrupts the search flow and forces the user to summon the keyboard again - only to repeat the same experience

Suggested Corrective Action

One of:

  • Revert to old behavior (keyboard stays until the search activation button is tapped) - it was decent
  • Make the delay configurable, don't forget the tooltip explaining where to go to change the behavior
  • (most complex) modify the UX in such a way that the keyboard stays in focus but search is executed in the background and the results are visible

Not To Get Up Twice

This deserves its own issue, but let me just briefly mention that the search results are rendered in a misleading and excessive way. It might be worth it to gray out or remove altogether the sections where there are no search results present, and revisit the count of 1 when the only result is "Empty" :)

Version Information

Squeezer 2.3.11, Pixel 7, Android 16

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions