183486 - navigating messages in standalone doesn't update thread pane highlight

Status: RESOLVED WORKSFORME

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[djk]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021201 Phoenix/0.4
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021202

I read messages in a standalone message window.

If I navigate to another message, the highlight in the thread pane remains on
the message which I originally opened in standalone.

It doesn't matter how I navigate to another message (menu, toolbar, keystroke),
nor which method of movement I use (Next, Next Unread, ...); the highlight does
not properly reflect the currently displayed standalone message.

Reproducible: Always

Steps to Reproduce:
1. Open MailNews
2. Doubleclick a message in the thread pane to bring up standalone message window
3. Using the standalone message window, navigate to another message.

Actual Results:  
Thread pane highlight remains on the message you doubleclicked.

Expected Results:  
The highlight should move to the currently displayed message.

This behavior is mentioned in bug 159412 comment 4 (2nd paragraph), as well as
in bug 163008 comment 1.

I felt that another bug needed to be opened to specifically address this
particular issue.

Finally, bug 172392 looks very similar, but it deals with standalone message
deletion.  If the patch in that bug works, maybe it could be adapted to fix this
bug as well.

Comment 1

[laurel]

longstanding issue (from day1)... not sure of bug number(s)

Comment 2

[Samir Gehani]

Laurel,
If this is a dupe has the original bug been nominated nsbeta1?  And if you find
the dupe could you close this out as a duplicate?  Thanks.

Comment 3

[laurel]

I'm not sure I'll find an original bug (too many variations in summaries), but I
know this has been like it currently is since day one of the mozilla/nav6 era. 
I found one fairly current duplicate... will dup it against this since this has
a little more (nomination) commentary.

So, I guess by Samir's comments he thinks this should be nominated?  Will
nominate this one then based on Samir's comment.  

Comment 4

[laurel]

Oh, FYI, a bit of history... never did this in Communicator 4.x either.

Comment 5

[laurel]

*** Bug 175612 has been marked as a duplicate of this bug. ***

Comment 6

[Samir Gehani]

Mail triage team: nsbeta1+/adt3

Comment 7

[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 8

[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 9

[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 10

[Jens Hatlak (:InvisibleSmiley)]

I suggest to close this bug as WONTFIX. Especially now with tabmail the standalone message window and the thread pane are completely decoupled as to what is shown or highlighted, only state changes like read/flagged etc. should be synced.

Comment 11

[Rainer Bielefeld]

NO longer reproducible with German SeaMonkey 2.32.1 Build 20150204202218 on German WIN7 64bit. My test:
1. From Task bar launch Seamonkey
   » Browser with start page will appear
2. Click envelope icon in Status Bar
   » MailNews will appear, Layout is "classic" with all 3 pqanes Accounts, 
     Subjects, Mail contents.
3. in left Accounts Pane Click the inbox folder of an account with unread
   messages in inbox
   » Summaries appear in Summaries Pane
4. If necessary: for Summaries Pane click "Date" heading to sort by ascending dates
5. If necessary: for Summaries Pane click "Thread" heading switch from
    thread vies to list view
6. In  Summaries Pane click a bold summary in a group of unread messages
   » Contents of message appears in right bottom Contents Pane
7.Double click selected Email in Subjects Pane
   » Stand Alone window with message appears
8. Menu 'Go  ► Next ► Message'
   » Contents of next mail appears 
9. With <Alt+Tab> switch back to Window with Classic View
   Expected: Double clicked Summary still highlighted, next summary should have
             changed from "bold= unread" to "normal=read" view
   Actual: As expected.

Also works fine with "Thread View" (Step 5)
Also works fine with Thunderbird 31.4.0