516467 - Message not marked as read when going to next message in standalone mail window [unread, space, button, n key]

Status: RESOLVED DUPLICATE of bug 514876

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Jens Hatlak (:InvisibleSmiley)]

With a current nightly build or SM 2.0 b2, when switching to another message in the standalone message window (by either using the N key, space bar or Next button) that next message is not marked as read. This is confirmed on both OS/2 and Windows and reported to be a regression from SM 2.0 b1. The 3pane window is not affected, it marks the message read under the same circumstances and respects the unread timer.

The problem is buried somewhere in the implementations of commands like cmd_nextUnreadMsg which are different from those in the 3pane window:

messageWindow.js case: performNavigation()
  performNavigation() -> LoadMessageByNavigationType()
    [didn't investigate further]

mail3PaneWindowCommands.js case -> MsgNextUnreadMessage()
  MsgNextUnreadMessage() -> GoNextMessage() in msgViewNavigation.js
    GoNextMessage() -> ScrollToMessage()
      ScrollToMessage() -> treeSelection.select()
        threadPane.js -> ThreadPaneSelectionChanged()
          ThreadPaneSelectionChanged() -> GetThreadTree().view.selectionChanged()
            [somewhere here mark message read is triggered]

Comment 1

[Robert Roessler]

This certainly *seems* to be the exact thing reported in bug 514876.