User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.2) Gecko/20090729 Firefox/3.5b4pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4pre) Gecko/20090910 Lightning/1.0pre Shredder/3.0b4pre When I search for a term, there is sometimes spam in the search results. It would be nice if I could just right-click on the message and select delete, or click on a "delete" icon, or whatever. Similarly, other actions might be sensible, like tagging the message, replying to it, or whatever. I don't understand why I have to switch to the list view to do that. Reproducible: Always

searchability of summary is a "good thing" - fixing. this is a fairly big usability issue as I stated in bug 518416 comment 0. The fact that no one else has picked up on it merelyiindcates to me that people aren't using the results list very much yet - but that''s the whole point of search. whether it's blocking is not for me to decide, but asking the question, blocking?

I agree on the fact that it should block - as without these manipulation finding the email is almost not useful.

Totally agreed it'd be great. But we won't block on this -- providing selection & operations on the search results is a huge amount of work, involving lots of strings & UI work. The "open as list" button (or whatever it's now called) is there primarily to support those use cases. We can incrementally improve the capabilities of the search results page in subsequent releases.

"Open as list" does the trick for search lists, but does not provide the following right-click actions: - Move message to - Copy message to - Move again to <last move made> - Delete - Label (and submenu) - Mark (and submenu) Those are present in the normal view right-click context menu. I usually use search to move emails from accounts, for example, lack of this context menu options renders the filtering useless for that purpose. I can understand that not-blocking, but it would really be good if at least those mising options were present in the search list view.

Thanks for following up. I had denied blocking for the bug as it applied to the search results list, but I didn't know those commands weren't available on the "show as list" view. It would indeed be very nice to fix that for release, as those operations are the reason for that view. I'll approve blocking, until someone convinces me it's way too hard.

(In reply to comment #6) > Thanks for following up. I had denied blocking for the bug as it applied to > the search results list, but I didn't know those commands weren't available on > the "show as list" view. It would indeed be very nice to fix that for release, > as those operations are the reason for that view. I've split out the context menu issue for the search results list (not the general view) into bug 519192 it should be reasonably easy to fix there and will save the original comment 0 issue getting lost. > I'll approve blocking, until someone convinces me it's way too hard. Now marking as blocking denied as all that remains for this bug is comment 0 and so comment 4 applies again.

Sorry for joining this party late, but can someone help clarify if/when TB will allow me to multi-select items from the Search "Show as List" view and move/copy them into folders? The other item I use that is note mentioned above is "Create Filter From Message". The current status is "blocking‑thunderbird3 denied", which seems to imply that it will not be fixed for the final version. However, this bug represents a regression from earlier builds and from TB2. The way I use search isn't just to find a message, but often to perform some action on that message (or messages). If there is a workaround, I'm all ears!

Bob: 1) hit "Open as list", and then 2) wait for bug 519192 to land =)

Sorry to have hijacked the original intent of the bug.

This WFM on 3.0rc1 build.

What exactly is the goal of this bug now?!

(In reply to comment #13) > What exactly is the goal of this bug now?! My bad . I read too fast.

(In reply to comment #13) > What exactly is the goal of this bug now?! Jens, Does the current bug summary match what you want the bug to achieve? Or, was the original primary intent of comment 0 that you want to be able to remove certain subjects/messages from the search results? (a worthy request IMO)

yeah, sounds good