Closed Bug 369643 Opened 18 years ago Closed 15 years ago

Auto-compact of folders (incorrectly) restores window state when it finishes

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: n1ck.h0w1tt+bugzilla, Unassigned)

Details

(Whiteboard: closeme 2009-06-18)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.2pre) Gecko/20070116 Thunderbird/2.0b2 ID:2007011615 When auto-compaction of folders completes it appears to restore the window state to where it was before it started. It should not do this. I have seen it manifest itself in 3 ways: 1 - If you switch to another application while auto-compact is running, TB steals focus and comes to the foreground when auto-compact finishes. 2 - If you select another message while auto-compact is running, when it finishes TB goes back to the message which was previously selected. This scenario is usually triggered when you delete a message and auto-compact starts. This means you end up going back to a message which was adjacent to the one you deleted. 3 - If you start scrolling down a message in the preview pane when auto-compact is running, when it finishes the message scrolls back up to the top. Again this scenario is usually triggered when you delete a message and auto-compact starts. TB selects the next message which you then read in the preview pane. Reproducible: Couldn't Reproduce Steps to Reproduce: 1. I cannot reproduce this as I cannot force auto-compact to be triggered. It may be possible by deliberately downloading a message with a large attachment, then deleting it. It may also be triggered be changing how long messages in a folder should be retained for (this may require a re-start of TB). 2. 3. Expected Results: The focus should never revert to where it was before auto-compact begins.
Assignee: mscott → nobody
Reporter, does this issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies? (1.5.0.x is now end-of-life and the latest supported 2.0.0.x is now 2.0.0.17)
Whiteboard: closeme 2008-11-06
It certainly did until recently. I am currently on version 2.0.0.17 (20080914). The problem I have is trying to force TB to auto-compact. I do not know how to do it. I go so fed up with it that I now use the Expunge addon to stop TB from compacting the folders directly after the initial download of e-mails when the program starts.
Whiteboard: closeme 2008-11-06 → qawanted
(In reply to comment #2) > It certainly did until recently. I am currently on version 2.0.0.17 (20080914). > The problem I have is trying to force TB to auto-compact. I do not know how to > do it. > > I go so fed up with it that I now use the Expunge addon to stop TB from > compacting the folders directly after the initial download of e-mails when the > program starts. Nick, thanks so much for the info - could you also please confirm if it still occurs with Thunderbird 3 beta 2? http://www.mozillamessaging.com/en-US/thunderbird/3.0b2/
Whiteboard: qawanted → closeme 2009-06-18
3-rd problem in comment #0 is reported to Bug 479064(observed with Seamonkey 1.1.5 too).
No longer blocks: 479064
For 3-rd problem with Tb trunk. (1) Shift+Delete of some mails. Sort by "Order Received" column, ascending order. (2) Restart Tb. (same profile is used by Tb 2 & Tb 3) (3) Click the folder at Tb window-1(=> No mail is selected). Scroll to bottom. (4) Open Tb window-2, Right click of the folder, "Compact Folder" (5) Return to Tb window-1. Tb 2.0.0.21 : Moved to top. Tb trunk(2009/6/01 build) : Stayed at bottom. As for 3-rd problem, WORKSFORME with Tb trunk.
Sorry, but I can't really comment as I never could trigger folder compaction on demand. You also caught me in the throws of moving my accounts over to IMAP. I tried on my last POP account by moving a 2MB mail message around. I may have triggered file compaction once and briefly seen my second scenario, but I am not sure and I could not force a compaction again (as far as I could see). On the other hand, if folder compaction is now a background task, perhaps I was triggering it and it was working OK. I have now completed my transition to IMAP so I cannot test any further.
FYI. 3-rd problem in comment #0 is reported to Bug 423763 too(for Tb trunk 2008/9/24 build). (In reply to comment #6) > I never could trigger folder compaction on demand. If IMAP, "Shift+Delete" followed by "Compact Folder" invokes EXPUNGE of mails with \Deleted flag. If POP3(local mail folder), you can do "folder compaction on demand" by "Shift+Delete" followed by "Compact Folder", with next settings. > mail.prompt_purge_threshhold = true/false => any of true or false > mail.purge_threshhold = NNNN (threshold value in KB, default=100KB) > mail.purge.ask = true/false => Change to true If you set prompt_purge_threshhold=true and restart Tb, You can cancel auto-compact by "Cancel" reply. (I recommend you to put it in user.js, because it can be set to false at dialog.) Note: If small purge_threshhold value, dialog is displayed frequently and it's annoying. Increase the value. > I have now completed my transition to IMAP so I cannot test any further. "Local mail folder" case can be tested very easily by dummpy POP3 account(No Global Inbox use), if "communication with POP3 server"/"Filtering upon download" is irrelevant. My Comment #5 is result of test with this setup.
"set prompt_purge_threshhold=true and restart Tb" should be "set MAIL.PURGE.ASK=true and restart Tb". Sorry for spam.
No response to last comments -> Incomplete. Please reopen if necessary, giving reasons why.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
My problem is that when it finishes compacting, it leaves the folder blank until you click somewhere else and come back. I recall seeing others had this problem also, but don't know if it is a different bug or this one. Still doing this up to version.23
You need to log in before you can comment on or make changes to this bug.