Closed
Bug 585300
Opened 14 years ago
Closed 14 years ago
[faceted search] Need UI to point out incomplete results count for global search with > 400 results or suppressed duplicate messages (wrong, misleading, incorrect)
Categories
(Thunderbird :: Search, defect)
Thunderbird
Search
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 537856
People
(Reporter: thomas8, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: uiwanted)
(followup from bug 585094 comment 6)
STR
1 Search all messages (global search) with > 400 matching messages (according to bug 585094, comment 6)
alternatively,
2 Search all messages (global search) for messages that have duplicates in some other folder etc.
Actual result
both 1) and 2)
TB makes no indication whatsoever that the number of results given does not reflect the actual total number of matches
Exepected
need functionality and UI to indicate that number of results given is not the actual total number of matches
Reporter | ||
Comment 1•14 years ago
|
||
STR/Actual results:
For global searches with > 400 actually existing results, we usually stop at 400 and claim that there are 400 matches (on fancy faceted results).
Combining step 1 and 2 makes this even more misleading because we first limit the number of results to 400, and *after that* take out the dupes, which results in seemingly precise result counts like 395 (as I just tried on a folder that had > 5000 matches).
In the case of dupes (even for < 400 matches), we simply ignore the number of duplicate messages, e.g. in Sent, Archive or Backup folders, when calculating the result count.
Blocks: 585094
Summary: [faceted search] Need to indicate correct result count for global search with > 400 results or suppressed duplicate messages (wrong, misleading, incorrect) → [faceted search] Need UI to point out incomplete results count for global search with > 400 results or suppressed duplicate messages (wrong, misleading, incorrect)
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•