Page MenuHomePhabricator

Search failures are not handled well by Codex TypeaheadSearch and MobileFrontend search
Open, MediumPublic

Description

Type S character
Throttle to offline
Type A character
Throttle to WiFi
Expected: Search for A should retry or an error should show or nothing should happen
Actual: Spinner shows after several seconds and never clears

Demonstration of issue in mobile

freezesearch.gif (447×549 px, 580 KB)

Codex issue

In Codex feedback whatsoever is given.

searchfeedback.gif (203×906 px, 84 KB)

Event Timeline

Jdlrobson triaged this task as Medium priority.Aug 24 2016, 5:18 PM
Jdlrobson added a project: Design.

Nirzar how do we want to report losses in connectivity?

@Nirzar Needs design analysis for both production version and new beta search overlay

@Nirzar: While your thinking about this problem, also bear in mind changes to other UI elements that we might want to make if we detect that the user has lost connectivity, e.g. the search bar and the talk button.

I'm not suggesting that we increase the scope of this task but that this task is part of a larger design epic.

Jdlrobson renamed this task from Search failures are not handled to Search failures are not handled well.Jul 10 2017, 11:21 PM
Jdlrobson updated the task description. (Show Details)

@Jdlrobson not sure why Herald decided to revive this task for DST, but can this be closed?

Jdlrobson renamed this task from Search failures are not handled well to Search failures are not handled well by Codex TypeaheadSearch and MobileFrontend search.Aug 3 2023, 8:17 PM
Jdlrobson updated the task description. (Show Details)

This issue is still a problem in the existing mobile search and the new Vector 2022 search. The reason I'm keeping them batched together is we're hoping at some point to replace the MobileFrontend version with the Codex version but this would require bug fixes (like this one) to occur in the Codex search first.