Closed Bug 200625 Opened 22 years ago Closed 22 years ago

"Save Image As" redownloads image even after image has completed loading

Categories

(Toolkit :: Downloads API, defect)

x86
All
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 120809

People

(Reporter: goi, Assigned: bugzilla)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401 Phoenix/0.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401 Phoenix/0.5 When I choose to save a loaded image, often the browser will redownload the image instead of saving it from the cached version. Some sites work(for example, http://goi.carnasaur.com/images/screenshots/unreal2.jpg), others like the listed one doesn't. Reproducible: Sometimes Steps to Reproduce: 1. Open the page/image file in the browser 2. Wait for it to finish loading 3. Choose "Save Image As" to save the image, continue to save as usual Actual Results: The "Save Picture" dialog will take longer than usual to appear, and once "Save" is chosen, the progress bar will appear, and the file will take a longer time to redownload. Expected Results: The file should be saved from cache, thus eliminating the need for redownloading, which wastes time.
Whiteboard: DUPEME
phoenix bug
Assignee: asa → blaker
Component: Browser-General → Downloading
Product: Browser → Phoenix
Target Milestone: --- → Phoenix0.5
Version: Trunk → unspecified
Target Milestone: Phoenix0.5 → ---
I don't think its a phoenix bug. I can reproduce it with Mozilla as well. Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 I've left the product as Phoenix(someone else moved it there), since I'm not sure exactly where to commit the bug too.
Keywords: qawanted
*** This bug has been marked as a duplicate of 120809 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Keywords: qawanted
OS: Windows 2000 → All
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
v
Status: RESOLVED → VERIFIED
Product: Firefox → Toolkit
I think that the real cause is that the image was not cachable. In this case, the real bug is bug 288462 (still open, contrary to bug 120809, which concerned really cached images). So, this bug should be marked as a duplicate of bug 288462.
You need to log in before you can comment on or make changes to this bug.