265431 - on imap folders, compacting a folder in offline mode breaks with external extensions

Status: RESOLVED EXPIRED

(Thunderbird :: Mail Window Front End, defect)

Description

[Slyoldfox]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.3) Gecko/20041010 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.3) Gecko/20041010 Firefox/0.10.1

I have no idea if this is an issue for the Thunderbird bug-list or more a bad
working extension. I have the purge.xpi extension installed to easier hit a
button instead of right clicking for "Compact folders" item.

With IMAP folders, in offline mode, the "compact folders" is disabled in the
menu item. However, the (bad) extension does not disable the widget. This allows
me to execute a compacting (in offline mode) on the IMAP folder. Of course this
does not make sense and Thunderbird displays a "Compacting Inbox" message, but
not really doing much and making Thunderbird instable when changing folders or
compacting again.

Reproducible: Always
Steps to Reproduce:
1. Install purge extension (texturizer.net/thunderbird/extensions/#purge)
2. Put yourself offline
3. Delete some mail
4. Hit purge button

Actual Results:  
Instable behaviour of thunderbird, escpecially when compacting again on the same
folder while it is still "busy"

Expected Results:  
Since external apps can execute a purge action, I would suggest a popup window
that mentions that a compacting cannot be done in offline mode. Maybe with an
added option to go "online"

Comment 1

[Mike Cowperthwaite]

xref bug 257273

Comment 2

[Slyoldfox]

It is close to the bug mentionned by Mike, however not the same. It's the fact
that "Purging" by extensions is still possible when being Offline, instead of
alerting the user that he is offline and can't purge when being offline.

Still occurs in version 0.9+ (20041106).

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.