181223 - Save Target Link as... asks for the File name but does NOT save the File !

Status: VERIFIED DUPLICATE of bug 171441

(Core Graveyard :: File Handling, defect)

Description

[Reimer Bonitz]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2b) Gecko/20021016
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2b) Gecko/20021016

tried to save the userChrome.css by Save Link Target as, didn't work
tried to save a pdf from www.warentest.de didnt work either.


Reproducible: Always

Steps to Reproduce:
1. Right-Klick a Link to a PDF or any other Filetype
2. Choose Save Link Target as...
3. Specify Filename and folder
4. Choose Save
5. try to find the file you saved
Actual Results:  
you dont find the file

Expected Results:  
it should have saved the file

Comment 1

[Matthias Versen [:Matti]]

>Expected Results:  
>it should have saved the file

you should do this before you file a bug :
a) read the bugzilla helper page. You used it (to file this bug) and and there
is a iframe.
Why Do you don't read #1 in this list ?
(summary: Unable to download files { "...could not be saved, because the source
file could not be read."; save as broken }) 

b) always read the release notes
c) always search before you file a bug

you will find a solution in the bug (if you read the bug header)

*** This bug has been marked as a duplicate of 171441 ***

Comment 2

[Daniel Wang]

bug fixed in 2002-10-24

--
to borrow from Wesha in bug 181084 comment 2:

User-Agent:       Very Impatient

Problem Description: User submits yet another duplicate of the most frequently
reported bug.

Actual Results:  
1. User did not read the release notes at

2. User did not read the list of most frequently reported bugs at the top of
"File a bug" page

3. User did not search the bug database before submitting a bug

4. User installed Mozilla without uninstalling the previous version first.



Expected Results:  

1. User should read the release notes at
   http://www.mozilla.org/releases/mozilla1.2b/
   
2. User should check if the issue he's gonna report is present among frequently
reported bugs at the top of "File a bug" page
   http://bugzilla.mozilla.org/enter_bug.cgi?product=Browser&format=guided

3. User should search the bug database before submitting a bug to see if he's
gonna report an issue that is already known about
   http://bugzilla.mozilla.org/query.cgi

4. User should uninstall previous versions of Mozilla before installing new version