rem: var outlinerView = gSearchView.QueryInterface(Components.interfaces.nsIOutlinerView); 
context: function HandleDeleteOrMoveMessageCompleted(folder){        var outlinerView = gSearchView.QueryInterface(Components.interfaces.nsIOutlinerView);        var outlinerSelection = outlinerView.selection;        viewSize = outlinerView.rowCount;        if (gNextMessageViewIndexAfterDelete >= viewSize)        {            if (viewSize > 0)                gNextMessageViewIndexAfterDelete = viewSize - 1;            else                gNextMessageViewIndexAfterDelete = -1;        }        // if we are about to set the selection with a new element then DON'T clear        // the selection then add the next message to select. This just generates        // an extra round of command updating notifications that we are trying to        // optimize away.        if (gNextMessageViewIndexAfterDelete != -1) {            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.            var outlinerView = gSearchView.QueryInterface(Components.interfaces.nsIOutlinerView);            if (outlinerView)                outlinerView.selectionChanged();            EnsureRowInThreadOutlinerIsVisible(gNextMessageViewIndexAfterDelete);         }        else            outlinerSelection.clearSelection(); /* clear selection in either case  */}
meta: 9421	/local1/tlutelli/issta_data/temp/all_js/javascript/2006_temp/2006/9421/30bc136f665511d061c00cd0e563484af987e39a/SearchDialog.js/clean/mailnews/base/search/resources/content/SearchDialog.js