Open Bug 573220 Opened 15 years ago Updated 3 years ago

Download location pointing to the root of the drive is ignored ->default is then used

Categories

(Toolkit :: Downloads API, defect)

Other
OS/2
defect

Tracking

()

People

(Reporter: bugzilla, Unassigned)

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.9.2.4) Gecko/20100527 Firefox/3.6.4 Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.9.2.4) Gecko/20100527 Firefox/3.6.4 When trying to dowload a file to "d:" ,the file is downloaded to the default location. - which drive makes no difference- No matter how the prefs are used ,changing the default location to d: gives no result at all ,no download in this case. Only folders are working ,does not matter which drive. Tried : safe mode with no plugin's and new profile using checked "always ask to save files to" gives the same result ,only folders are accepted and the download is correctly done Reproducible: Always Steps to Reproduce: 1. check "save files to" and set to c: or d: (root of drive) 2. point to a file somewhere (type makes no difference) 3. download it Actual Results: downloaded to the default location which is set initially (a folder somewhere) Expected Results: downloaded to the given drive (root) All this happened when switching to firefox 3.5.8 to 3.6.2 or 3.6.4
Have you tried downloading to "d:\"? Just entering d: doesn't specify a directory and it seems correct for Firefox to not act on it.
Already tried that , besides i have used my D: drive for many years which several machines and it always worked till version 3.5.8 and before ,after that no more.
And it must be OS/2 related ,the windows versions do not have this problem
Can you test with a new profile? eg start Firefox -ProfileManager and create a new profile for testing.
Please see the original text ,already done that and more
(In reply to comment #5) > Please see the original text ,already done that and more Sorry, I missed that. Did you create a new profile with each version that you tried? Here I can only reproduce the behaviour with a profile that I know is broken. Also it only affects HPFS and JFS volumes. Works with FAT and RAMFS volumes. Since I don't have a 1.9.2 tree, I downloaded Firefox 3.6.8, created a new profile and the only problem was that making the default e: did not stick. Changing the download location in the file dialog does result in the file being saved to e:\ Can you retest with 3.6.8 including creating a new profile if you still have the problem? 3.6.8 is available at http://releases.mozilla.org/pub/mozilla.org/firefox/releases/3.6.8/contrib/firefox-3.6.8.en-US.os2.zip
O.K. This is my exact sequence what i did with 3.6.8 1:renamed my plugin dir to something different -to be sure a plugin causes no problem. 2:created a new profile 3:started with this profile 4:options-download-selected "ask where to save files to" 5:open a download location 6:choose where to download ==> drive d 7:presed o.k. result nothing happened as if i started nothing -no ..sec remaing in bar below- just nothing 8:tried thesame with another download location ==. drive g: result : also nothing 9:same download file but now i do not point at another location result: download starts (to the default of in my case the folder n:\warpzilla\download) Even on a completely new computer ,same problem
Sorry for being late replying, got distracted. While I find here that I can save to the root of all drives, I do have a problem making the choice stick. After forcing a save to I:\ I find the preferences has reverted to %MOZILLA_HOME%\downloads. Eventually the I:\ stuck and I tried changing it to e:\ and it kept changing back to I:\. This was true even when using about:config to change the default. So I'm left wondering if your problem is just part of a bigger bug with download locations which shows up differently on different systems. BTW what version of OS/2 (eCS) are you using and what file system(s) are you testing?
At least you have half my problem ,i did not mention before but i also can not make any root drive choice stick. Only when forcing it to a new root drive ,a download does NOT start. I have computer #1 ,my office machine with ecom 1.2 and now i am going to replace this one with #2 (in the future ,when all is working as it should),with freshly installed eecom 2.0GA But the behaviour is excactly thesame The filesystem to which i try to save makes no different ,tried hpfs ,jfs, netdrive,lan drive And tried as a test : share drive n:\warpzilla\....dowloads , map D: to this share And even now the download does not start It looks almost like for some reason the download location must be more than 3 characters "F:\" fail --- "F:\p" works
I believe I have seen problems saving to the root as well, but a quick test with Seamonkey 2.1b3 is working right now. Peter, have you tried with Firefox 4.0.1?
Yes ,tried it (and seamonkey) - both failed - even on another computer new profile with no addons.
Still see this with SeaMonkey 2.3.3; download to the root of any drive silently fails, and the download location for the next invocation has reverted to the default.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I see the same symptom as you describe in Comment 12, Steve (silent fail, then revert to default location on next try) under SM 2.7.2 and FF 10.0.2. That said, PmW-Fx 2.0.0.21 behaves as expected. I'd seen this before, but always by mistake, i.e., not drilling down the path to where I wanted to save the file, and hitting <Enter> too soon. until now, I thought I wasn't actually starting the download, but now I realize that it *should* have downloaded.
It's a strange bug, I just successfully downloaded files to 4 different root directories and now the download location is sticking as well.
Some additional things to add : Thunderbird 6.02 and up has the same problem saving attachments As trying to find aworkaround i tried use the extension "PDF download" and strangely enough it does work as it should -no problem saving a pdf file to c:\ or d:\ Also tried "DownThemAll" ,and here the problem still exists but at least it generated a red box saying: destination read only or invalid location. Maybe this helps in some way
log attached from DownThemAll"
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: