Closed
Bug 310216
Opened 20 years ago
Closed 17 years ago
Compose winow stops responding while downloading mail
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: alaric, Assigned: mscott)
Details
(Whiteboard: closeme 2008-08-28)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
The compose windowI becomes totally unresponsive whenever Thunderbird is
downloading mail. You can open a new compose window while mail is being
downloaded, but you cannot type, and the window will not refresh. This problem
has existed at least since 1.0.4. Control does not return to the user until all
mail has been downloaded.
Reproducible: Always
Steps to Reproduce:
Send yourself an arbitrary test message with a large file attachment, then check
your mail. While the message is downloading, open a compose window and try to
type a message or address it.
Actual Results:
You will be unable to compose or address any message while mail is downloading.
Expected Results:
Thunderbird is threaded. Surely it should be able to walk and chew gum -- er, I
mean, download and compose mail -- at the same time. I can READ mail while
other mail is downloading; why can't I write it too?
Sometimes, notably when first starting Thunderbird, the whole message-list
window is unresponsive as well until the initial batch of mail has been downloaded.
Updated•18 years ago
|
QA Contact: message-compose
Comment 1•17 years ago
|
||
Reporter, does the 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 2.0.0.16)
Whiteboard: closeme 2008-08-28
Comment 2•17 years ago
|
||
Reporter, does the 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 2.0.0.16)
Comment 3•17 years ago
|
||
RESO INCO per lack of response to the last question(s). If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
| Reporter | ||
Comment 4•17 years ago
|
||
Sorry, didn't receive the prior queries.
Using 2.0.0.14 or 2.0.0.16 I am currently unable to reproduce.
You need to log in
before you can comment on or make changes to this bug.
Description
•