delete from stand alone message window launched from search results doesn't follow search view. to reproduce: do a search. double click on an entry, you get the stand alone message window. hit delete. you should get the next element in the search results. you don't. (I'm not sure what you get right now, probably the view is just a folder view.) I bet the same is true for "Next".

Yes, this is how it's been. We never did implement the search view, just the folder view -- there might be an old bug about this... I'll check.

view got nsMsgSearchDBView, that's what we use for the results pane in search. I think we're not to far from making delete and next navigation work in std alone, if we use that view and not a nsMsgDBView but I'd have to investigate to see if that's possible.

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

still exists dec14 commercial trunk

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

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

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

Appears to be dependent on the "Close message window on delete" preference setting. With option enabled, operation is as described (the view is the "Search Results" list. With option disabled, operation is as desired. Mac OS X 10.5.8, TB 3.1.1.

If "Close message window on delete" is enabled, then the "delete/" part of the bug summary is not relevant?

Grrr. This bug is not actionable because there are no clear STR, Actual results, and Expected Results. Too many unknowns, sorry. (In reply to Wayne Mery (:wsmwk) from comment #9) > If "Close message window on delete" is enabled, then the "delete/" part of > the bug summary is not relevant? It might still be. If I use Advanced Search (Ctrl+Shift+F), [x] open msgs in new window instead tab, [x] close window after delete (not exact strings here, sorry), then from search results window, double-click on msg2 of 3, it opens in standalone win. Hit del. msg gone, msg window gone as expected. But focus in search results window is back on msg1, not selected. Perhaps it should be on msg3, selected. If comment 8 is right, which I can't tell bc I don't fully understand this bug, then I suspect original case of this bug has been fixed, which was probably doing STR without [x] close win after del, and then getting the next msg in msg standalone win in wrong sequence...