Bommels05/Mozilla
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Bug #112220 avoid an extra firing of the on select outliner handler when deleting

Browse Source 
a message. Supress command updating when selecting the next message
after a delete
r=bienvenu
rs=sspitzer


git-svn-id: svn://10.0.0.236/trunk@109032 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
mscott%netscape.com
2001-11-27 21:45:41 +00:00
parent 7dda0b46d1
commit a073137744
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
mozilla/mailnews/base/resources/content/msgMail3PaneWindow.js
View File

@@ -269,14 +269,14 @@ function HandleDeleteOrMoveMsgCompleted(folder)
// optimize away.
if (gNextMessageViewIndexAfterDelete != -1)
{
// when deleting a message we don't update the commands when the selection goes 0
// (we have a hack in nsMsgDBView which prevents that update) so there is no need to
// update commands when we select the next message after the delete the commands already
// have the right update state...
gDBView.suppressCommandUpdating = true;
outlinerSelection.select(gNextMessageViewIndexAfterDelete);
// since gNextMessageViewIndexAfterDelete probably has the same value
// as the last index we had selected, the outliner isn't generating a new
// selectionChanged notification for the outliner view. So we aren't loading the
// next message. to fix this, force the selection changed update.
if (outlinerView)
outlinerView.selectionChanged();
EnsureRowInThreadOutlinerIsVisible(gNextMessageViewIndexAfterDelete);
gDBView.suppressCommandUpdating = false;
}
else
{