Distinguish between search timeout and zero result searches
Bug #1573738 reported by
Jeff Godin
This bug report is a duplicate of:
Bug #1103321: tpac: "no entries were found" message can be misleading.
Edit
Remove
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Currently there is no visual difference to the end user between a search that has resulted in zero matches and a search that has resulted in a timeout on the backend.
It would be an improvement to distinguish between these two scenarios and display different messages to the user in each case.
| Changed in evergreen: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| tags: |
added: opac removed: tpac |
To post a comment you must log in.
