Open Bug 116075 Opened 18 years ago Updated 5 years ago
Quicksearch should not hide *threads* which contain search results (in threaded view)
Quicksearch should not hide *threads* which contain search results (in threaded view) if i am looking for a thread with a sender or subject, then i usually want to see the whole thread that applies to my search. This is particularly useful for "quickly" seeing if there are responses to my posts in newsgroups (i just enter my name in the quicksearch pane). The only disadvantage would be when there are very long threads, i may need to scroll through that thread to find the response to my post, but at least i would have eliminated many many other threads in large newsgroups (e.g., mozilla.general). If a view is threaded, then the entire thread should remain visible. If a view is unthreaded, then the current behaviour is good. This would be much more flexible in handling te way the user is likely to want to see the info he is looking for.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee: naving → sspitzer
Status: ASSIGNED → NEW
couldn't agree more - this is the default behaviour in Kmail and it's almost essential behaviour when working with mailing lists. http://forums.mozillazine.org/viewtopic.php?t=440205&highlight=
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
another good item for Thunderbird:Search wiki. And I think "seek" provides this (or took it as a request). I don't have it running ATM to check. funny target milestone
Component: MailNews: Filters → MailNews: Search
QA Contact: laurel → search
I think some means of giving the user the choice would be nice. This is probably just one of many use cases: Threads sometimes drift, and when this happens, the subject line sometimes changes. The current behaviour makes it possible to pick out the branch in which the subject has changed, or even to cut out a fair portion of the drift and focus on the original topic.
I'd love to see this implemented.
You need to log in before you can comment on or make changes to this bug.