Comment 4 for bug 590834

Maybe the search-routine was invoked - that's an internal technical view. If the search function can only be applied to text (which is the case here) then evince should try to be "smart about it" when no object (text) for the function (find) is available.

I installed acrobat reader to see if it does what I'm suggesting but it doesn't.
It acts as if it's busy searching through the file with the result: "no matches found".
But I found a function in acrobat reader under Document, Accessibility Quick Check and this function, if let loose on the same document comes up with the result:
 "This document appears to contain no text. It may be a scanned image." Oh, and how right it is!
Now if this function could be called when the document is loaded, then if I press ctrl-f (or select Edit, Find) I could be presented with a grayed, not writable search-box and with the message:
 "This document appears to contain no text. It may be a scanned image." (So give up trying to find something, dummy!)
I like apps that are smart about what they're doing.

I'll be more precise (and concise) about the bug:
Any filetype that can be shown with evince that does not have any (via ctrl-f or edit,find) searchable content, shouldn't
 - display the search-bar
 - allow inputting a search term
 - and return "0 found on this page"
as though a search had taken place.

I know this might not be the most important issue on the planet. I just stumbled across it and thought I'd let you know. If you think no action needs to be taken, I can accept that.