When doing a body search on IMAP on windows or mac, the total results only briefly appears in the status bar and then disappears. This is not a problem for local searches.

it's strange 'cause it's only body searches in the quick search drop down that get the status text cleared.

For local and hdr (subject/sender) searches, the quick searches happen so quickly, we never bother to start the progress meteor. In the case of an IMAP body search, it does take a while, so we do end up starting the meteors. And every time we stop the meteors, we clear the status text in the status bar: http://lxr.mozilla.org/mozilla/source/mail/base/content/mailWindow.js#386 I'm not sure we have enough context information in the status feedback code to not clear this value when performing a quick search. I'm not sure how bad it would be if we removed the code that clears the status text all together when the meteors stop. That would make it so we always leave the last piece of status information in the status bar. Such as "Downloading message..." even when we are done downloading a message. or "Compacting folder Inbox..." even when we've finished compaction. So that would probably be bad. Hmmm.

gonna have to punt.

Doesn't seem to happen always. I never see it after a few searches, but I think the first search I tried showed it.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5pre) Gecko/20091008 Shredder/3.0pre I don't see "3 matches found" status bar message ever, neither on pop3 nor imap filtering. --> morphing summary. We used to show that in TB2. IMO number of quicksearch filter matches should be shown on the right, and it should stay for as long as the filter is active.

"Searching..." is what I see now in status bar with current trunk - both for local and imap.

Related discussion in Bug 489588, starting from Bug 489588 Comment 5

Noting that if all sorts of message sources use the same display area, then any source that either posts or -clears- the message window will obscure information. Something to be said for either: normalizing the relation between message location and source (ie, have 1-to-1 source and window definition), such that if two concurrent messages are posted, they do not land in the same place, and they have separate decisions trees for clearing.