I just tried this again, now on 3.1.2 (other info same as Comment #24); the window displaying the message is closed, the selector in the message-list window advances to the next message, but no window is opened.
Is the desired behavior (and the subject of this RFE) that described in Comment #20, and if so, what would be the rationale for not selecting ANY message in the message list ? Or is the desired behavior the negation of that described in Comment #21 (which would appear to me to be a bug) ?
Differences between my test and that of Comment #25: Message contained in "Local Folders" subfolder vs. IMAP folder, TB3.1.2 vs. TB3.0.4.
Bug 498141 (opened because "Close message window on delete" got broken) makes mention of the IMAP option to "just mark as deleted" somehow having an effect -- but it's not clear (without a much closer examination of the patch) whether the fix for Bug 498141 accommodated that case. The last comment in Bug 498141 requests re-opening or that bug, indicating that the preference was still broken; Comment #21 and Comment #25 here indicate the same, based on an as-yet-to-be-determined condition (that I apparently don't have).
I just tried this again, now on 3.1.2 (other info same as Comment #24); the window displaying the message is closed, the selector in the message-list window advances to the next message, but no window is opened.
Is the desired behavior (and the subject of this RFE) that described in Comment #20, and if so, what would be the rationale for not selecting ANY message in the message list ? Or is the desired behavior the negation of that described in Comment #21 (which would appear to me to be a bug) ?
Differences between my test and that of Comment #25: Message contained in "Local Folders" subfolder vs. IMAP folder, TB3.1.2 vs. TB3.0.4.
Bug 498141 (opened because "Close message window on delete" got broken) makes mention of the IMAP option to "just mark as deleted" somehow having an effect -- but it's not clear (without a much closer examination of the patch) whether the fix for Bug 498141 accommodated that case. The last comment in Bug 498141 requests re-opening or that bug, indicating that the preference was still broken; Comment #21 and Comment #25 here indicate the same, based on an as-yet- to-be-determine d condition (that I apparently don't have).