image does not save when selecting from webpage when selecting 'save image as'

UNCONFIRMED
Unassigned

Status

()

UNCONFIRMED
11 years ago
3 years ago

People

(Reporter: jdavison, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5

After upgrading to Firefox 3 Beta 5, images are no longer saved when I select 'save image as' by right clicking on the image.  The save image window is opened, but after selecting a save location, nothing is saved or shown in the download manager.

Reproducible: Always

Steps to Reproduce:
1.Find image to save.
2.Right click image and select 'save image as'
3.Select location to save image
Actual Results:  
No image is saved to selected location

Expected Results:  
Image should be saved to selected location

Comment 1

11 years ago
WFM on the Trunk, have you tried in safe mode or with a clean profile?

Comment 2

11 years ago
I'm using Firefox 3 Beta 5 on Windows XP SP 2 and here everything works fine. I tried both, keeping the original filename and giving a new file name, it both works.
(Reporter)

Comment 3

11 years ago
using Firefox 3 Beta 5 on Windows XP SP 2, error was occurring after laptop had been in standby mode overnight.  It has happened twice now, but rebooting Windows corrects this.  I shouldn't have listed it as always reproducible.
(Assignee)

Updated

10 years ago
Product: Firefox → Toolkit

Comment 4

10 years ago
Just want to say I have the same problem but using FF 3.0.3! Everytime I try to save an image - nothing happens. In the error console I get this message

Error: uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIDownloadManager.userDownloadsDirectory]"  nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)"  location: "JS frame :: chrome://global/content/contentAreaUtils.js :: getTargetFile :: line 439"  data: no]

I hope it helps, this is a big problem!
You need to log in before you can comment on or make changes to this bug.