Closed
Bug 517663
Opened 16 years ago
Closed 16 years ago
Reply/Forward/Tag (1-5) operate on initial message in standalone message window
Categories
(SeaMonkey :: MailNews: Message Display, defect)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 514876
People
(Reporter: InvisibleSmiley, Unassigned)
Details
(Keywords: regression)
Reply (All), Forward and tagging (using keys 1-5) all operate on the message that the standalone message window has been opened with in the beginning. At least that's what it seems like, it's neither the current message that you see after navigating to another message nor the message currently selected in the thread pane if you changed the selection there.
This is most probably a regression from bug 460960 (tabmail). See bug 514876 for a another case.
Short analysis:
All three methods above eventually call GetLoadedMessage() in messageWindows.js which returns gCurrentMessageUri. It seems that variable is not updated correctly (any more). It is set by messagepaneObserver.onDrop(), nsMsgDBViewCommandUpdater.displayMessageChanged(), OnLoadMessageWindow(), and reset by ClearMessageSelection().
Flags: wanted-seamonkey2.0?
Comment 1•16 years ago
|
||
Wanted for sure, possibly this could even be blocking, but I suspect it could easily end up as a dupe of bug 514876 in the end for having the same root cause.
Flags: wanted-seamonkey2.0? → wanted-seamonkey2.0+
Comment 2•16 years ago
|
||
Yes, dupe of bug 514876.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Updated•16 years ago
|
Flags: wanted-seamonkey2.0+
You need to log in
before you can comment on or make changes to this bug.
Description
•