nextcloud / nextcloud/server

[Bug]: search in progress shouldn't say "No matching results"

Open
#57,678 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3. to review 33-feedback bug feature: search
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
Bug description

While a search (Unified search) is still in progress, it should NOT show "No matching results".
This is misleading, indicating that the search is finished and it won't help to continue waiting for results.

"Search in progress..." would be a much better label.

Steps to reproduce
  1. click the "Unified search" on the upper right
  2. type a string which will only be found in files, not in contacts or anywhere else (at least on my instance with many, many files it takes the longest to find a file)
  3. you'll see "No matching results" for a couple of seconds until results start appearing
Expected behavior

Simple show "Search in progress...". Only switch to "No matching results" finally no results have been found and further waiting can't yield results.

Nextcloud Server version

33.0.0 beta 5

Additional info

See also:

  • #41651
  • #45946

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start from the Unified search interface and reproduce the reported delay using a query that returns file results slowly. Trace how the interface distinguishes an in-progress search from a completed search with no results. Done means the pending state shows “Search in progress...” and “No matching results” appears only after the search finishes empty.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.