Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 366755 - Search 0 matches reported for 8 files
Summary: Search 0 matches reported for 8 files
Status: CLOSED DUPLICATE of bug 366212
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 0.4   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-14 16:27 EST by John J. Barton CLA
Modified: 2012-01-12 09:56 EST (History)
2 users (show)

See Also:


Attachments
See it (35.45 KB, image/png)
2011-12-14 16:27 EST, John J. Barton CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description John J. Barton CLA 2011-12-14 16:27:05 EST
Created attachment 208407 [details]
See it

When I search the UI often says "(0 matches)" It makes no sense.
Comment 1 Andrew Eisenberg CLA 2012-01-11 19:22:11 EST
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?
Comment 2 John J. Barton CLA 2012-01-11 19:40:55 EST
I've not seen this problem lately. The search UI changed quite a lot; I guess this is now fixed.
Comment 3 libing wang CLA 2012-01-12 09:26:35 EST
(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.
Comment 4 John Arthorne CLA 2012-01-12 09:56:34 EST
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 ***