Bugzilla – Full Text Bug Listing
| Summary: | Search 0 matches reported for 8 files | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | John J. Barton <johnjbarton> | ||||
| Component: | Client | Assignee: | Project Inbox <orion.client-inbox> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | andrew.eisenberg, libingw | ||||
| Version: | 0.4 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Is the problem that the UI is erroneously specifying "(0 matches)" when there really are matches, or that you expect files without matches to not appear in the list at all? I've not seen this problem lately. The search UI changed quite a lot; I guess this is now fixed. (In reply to comment #2) > I've not seen this problem lately. The search UI changed quite a lot; I guess > this is now fixed. Yes, we've improved this area. I think bug 366212 addressed the similar issue, which's been fixed already. This can still happen, because the server side indexing might lag behind the actual file contents. So, the server reports a matching document, but when we parse it on the client side we don't find any matches because the file was changed since it was indexed. Libing improved the presentation for this case by greying out such matches in the search results. I think we can close this. *** This bug has been marked as a duplicate of bug 366212 *** |
Created attachment 208407 [details] See it When I search the UI often says "(0 matches)" It makes no sense.