191298 - (watch-ignore-icon) [META] Tracker for watch/ignore icon problems

Status: NEW

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Stewart Gordon]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2) Gecko/20021126
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2) Gecko/20021126

This is a tracker for bugs connected with the displaying of the icon showing the
watched or ignored status of a newsgroup message thread.

Reproducible: Always

Steps to Reproduce:

Comment 1

[Stewart Gordon]

Bug 122650 - Icon is never removed once a thread is unignored/unwatched.
Bug 123047 - Watch/Ignore: Incorrect icon display in this case of
Watch-Ignore-Unignore
Bug 132572 - Watched Thread icon doesn't display in next session
Bug 183013 - holding K to ignore multiple threads doesn't work, only ignores the
first few (actually, it only shows the ignore icon on the first few)

Maybe all these bugs are reducible to a general one.  Or maybe not.

Several other bugs fitting the bill are already marked as "fixed" or
"duplicate".    Do these want to be listed here?

Comment 2

[Matthias Versen [:Matti]]

tracker -> reporter

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 4

[Stewart Gordon]

Trying to expire a meta bug doesn't make any sense - we need to look at the dependent bugs individually.