Closed
Bug 594805
Opened 15 years ago
Closed 14 years ago
Attach file picker and Unresponsive Script don't mix
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 482811
People
(Reporter: zandr, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b5) Gecko/20100101 Firefox/4.0b5
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100825 Thunderbird/3.1.3
If you set out to attach a file using the file picker (as opposed to drag-n-drop), and then get sidetracked, the unresponsive script warning will fire, but leave you in a state where a force-quit is the only way out.
Reproducible: Sometimes
Steps to Reproduce:
1. Compose a message.
2. Click attach.
3. Change focus to another application.
3. Wait. Usually around 5 minutes, and it seems to happen faster if the machine is idle. In trying to reproduce this to write up this report, I've succeeded 5 out of 7 times.
Actual Results:
On switching back to Tbird, the file picker will have focus, and the unresponsive script warning will pop up in a sheet from the compose window.
Script: chrome://messenger/content/messengercompose/MsgComposeCommands.js:3814
The behavior at this point is downright weird. The file picker works, in that you can browse the file system, but clicking either Open or Cancel does nothing. The button widget responds, but nothing happens. Clicking either of the buttons on the unresponsive script sheet is useless, as it doesn't have focus.
Curiously, sending a Quit to the application through the dock will change focus to the compose window, but the buttons on the unresponsive script sheet are still useless. Force Quit is the only way out.
Expected Results:
You should be able to either dismiss the unresponsive script sheet, or choose open or cancel in the file picker.
Or, the sheet shouldn't pop up at all, but fix that second. :)
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•