Closed
Bug 331768
Opened 18 years ago
Closed 18 years ago
Browser hangs several seconds after confirming save dialogue
Categories
(Toolkit :: Downloads API, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 159107
People
(Reporter: simon.reinhardt, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 When trying to download a file, going to the save dialogue and then clicking on "Save" the whole application hangs for several seconds until the download manager pops up. Reproducible: Always Steps to Reproduce: Any step that leads to starting a download: 1. right click on a URL and select "save target as" 2. confirm save dialogue or 1. left click on an URL that will automatically lead to the "open" dialogue 2. either select "open with" or "save to hard disc" and confirm Actual Results: The application hangs for several seconds, then the download manager pops up. Expected Results: Show the download manager immediatly? :)
Comment 1•18 years ago
|
||
Sounds like an old Linux bug, but since you're on windows, and it was fixed in 1.5.0.1, it can't be that :) Does it happen for all files? Is your download list empty? Are you saving to a network drive or anything?
Reporter | ||
Comment 2•18 years ago
|
||
(In reply to comment #1) > Does it happen for all files? Is your download list empty? Are you saving to a > network drive or anything? It happens for all files, I'm storing locally. But now that you mention it, the download list was very long. I cleared it and now it shows immediatly. Never thought about that. Though still somehow annoying it takes so long to build that list. :)
Comment 3•18 years ago
|
||
Dupe of bug 159107 as per bug 242604 *** This bug has been marked as a duplicate of 159107 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•