Closed
Bug 441893
Opened 16 years ago
Closed 15 years ago
AOL emails with attachments - attachments cannot be opened or saved
Categories
(Toolkit :: Downloads API, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: tmolitors, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14 An email with an attachment: the email can be opened and read, but the attachment cannot be opened or saved. After clicking on the attachment, the Firefox "You have chosen to open..." dialog box appears with its options ("Open with...", "Save to Disk", "Do this automatically..."), but the "OK" button is disabled. The circling dots in the upper right-hand corner are constantly "spinning", indicating a running process along with a "Transferring data from aolmemwebmail.122.2o7.net..." message along the bottom edge of the screen. This problem is consistent across numerous (50+) emails with attachments and began a few weeks ago. Quiting Firefox and using IE7, the emails and their attachments function properly (i.e., the email attachments are not corrupt). Reproducible: Always Steps to Reproduce: 1. Using Firefox, go to www.aol.com 2. Log into AOL's email 3. Find an email with an attachment 4 [review]. Left-click on the attachment 5. Wait and wait and wait for the "OK" button to enable Actual Results: I waited and waited and waited and waited. After waiting, I clicked on the "Cancel" button of the "You have chosen to open..." dialog box. It closed and I continued working on other things. Expected Results: The download should have proceeded.
Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
Comment 1•15 years ago
|
||
IS this till an issue with Fitrefox3.5 or later ?
Comment 2•15 years ago
|
||
No response to comment 1, closing as incomplete.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•