Closed Bug 224634 Opened 18 years ago Closed 16 years ago

News: A killed (Ignored) thread should be completely hidden


(SeaMonkey :: MailNews: Message Display, enhancement)

Windows XP
Not set


(Not tracked)



(Reporter: superbiskit, Unassigned)


User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031030 Firebird/0.7+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031030 Firebird/0.7+

If I select "Ignore Thread," the usual reason is that it is Junk (at least to
me).  Likewise if I program a junkfilter to do it for me.
I would much prefer to see no trace of it thereafter and forever.  With a mild
grumble, I would accept this as a preference.  

As it stands, it's hard to see what use the "Ignore Thread" has.

Reproducible: Always

Steps to Reproduce:
1. Select a newsgroup thread
2. 'K' (Message->Ignore Thread)

Actual Results:  
The message title is unbolded

Expected Results:  
Hidden the thread from view completely unless I select View->Messages->Ignored
Ignore Thread *does* collapse the thread, and the ignored thread *is* invisible 
on subsequent views of the group.  So it is of *some* use as written.

The reason to *not* hide immediately is in case the 'K' is typed accidentally; 
you might not even notice that you'd killed a thread of interest.
Severity: normal → enhancement
Blocks: 236849
Product: Browser → Seamonkey
then why not add a more 'naughty' option which would not be binded on the keyboard ?

When I delete a mail, i dont see it any more. I thought TB as a unified reader.
And I expected him to be able not to show anymore messages I dont want to see.
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Closed: 16 years ago
Resolution: --- → EXPIRED
No longer blocks: 236849
You need to log in before you can comment on or make changes to this bug.