Conflicts with sticky headers and search fields

What it is

Many lists pin a search field, a segmented control, or a large title at the top. A downward pull may be refresh, or pulling a hidden search into view, or just focusing the field. When sticky chrome and refresh both claim the same overscroll trace, people cannot tell whether lift will refresh, expand search, or park the caret in the field.

Why it happens

Sticky search often uses “keep pulling to expand”: past another negative threshold the bar grows from collapsed to full. Refresh also occupies negative offset. If the two thresholds sit together, or share one damping stretch, the classifier only names a winner at lift. Focusing search wants a short tap; if the refresh recognizer treats any downward motion at the top as overscroll, that tap is stretched into a failed refresh animation. Collapsing large titles also change the top geometry while scrolling down, so the refresh hit region moves, and the first and second pulls do not start on the same pixel.

Studying it

Run three tasks: refresh, expand and use search, tap into the field and type. Top structures: no sticky, search only, search plus large title. Log cross-misfires. Spread the two negative thresholds as an independent variable. Eye tracking shows whether people stare at the spinner region or the search bar while pulling.

Where it stops holding

When search is always large and does not expand on pull, the clash shrinks to “tap search versus refresh passing over it,” which slop can split. A search-only page with no list often has no use for pull-to-refresh. Landscape shortens the top, so sticky and refresh crowd into the same centimetre.

Applying it

• Give expand-search and refresh two well-separated negative thresholds, or put search on an explicit handle or tap and arm refresh only on overscroll from empty top area.
• A short tap on the search field must not start a refresh animation.
• Ask people to “go search a word” and to “go pull new.” If the search task sees a spinner first, or the refresh task opens the search keyboard, the top trace is over-written by two meanings.

Related

• Same group: C3.15.1 Pull-to-refresh attaches to overscroll at the top of a list · C3.15.2 Crossing the trigger threshold needs feedback · C3.15.4 The gesture becomes redundant under auto-refresh
• Adjacent: C3.07 Pan · C6.06 Soft keyboards and screen occupancy
• Search: sticky header · search bar conflict · large title