Watched threads view opens with new msg, not necessarily threaded.

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: laurel, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
Using jan30 commercial trunk build

The Watched Threads with Unread view should always open as threaded, show the
entire thread of those threads with unread items.  Here's a general case where
we show only new items and they're not threaded.

Steps:
1.  Open newsgroup, threaded mode, show All.
2.  Message|Watch Thread on a thread having replies and at least one message in
the thread is unread.
3.  Switch the view to View|Watched Threads with Unread.  View opens in threaded
mode, shows the entire thread which has an unread item.
4.  Read all unread items in the thread.  If you happen to have any other
watched threads, read all unread items in those, too.  So you want to have no
unread items left in any watched threads.
5.  Switch the View back to All, then switch back to Watched Threads with
Unread.  The Watched view is now empty.
6.  Collapse the news server or select another newsgroup.
7.  From another machine send a reply to the thread you have watched.
8.  Now expand the news server, go to the newsgroup which you left in the
(empty) watched view.  When the newsgroup shows the newly received reply it is
added to the view, but just the new message is shown and not the full thread. 
If you've received a few new replies to the thread, they'll all be shown but
will not be threaded and still the entire thread will not be shown.

Result:  A group left in an empty, threaded Watched Thread view will open next
time to show new messages in the watched thread, but will not be threaded.

Expected: Watched Threads with Unread view should always open threaded, full
thread in view.
(Reporter)

Updated

16 years ago
QA Contact: esther → laurel
Sounds very much like a dupe of bug 98183?

Updated

14 years ago
Blocks: 236849
Product: Browser → Seamonkey

Updated

13 years ago
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: laurel → message-display

Comment 2

9 years ago
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
Status: NEW → UNCONFIRMED

Comment 3

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.