Open Bug 1468827 Opened 7 years ago Updated 3 years ago

file not present after doing save-as

Categories

(Firefox :: File Handling, defect, P3)

60 Branch
Unspecified
Linux
defect

Tracking

()

People

(Reporter: gideon425xx, Unassigned)

Details

I am using firefox version 60.0.1 on Linux. The problem seems to reproduce each time. Other similar links do not have the problem. 1. visit this link https://www.dailykos.com/stories/2007/12/31/428559/- 2. wait for a few seconds 3. click on file and then "save page as" 4. enter y.html and hit return 5. wait for download to complete 6. check the download directory expected results: the y.html file is present actual results: the y.html file is not present
I couldn't reproduce on OSX with 60 or 62, so marking as Linux. I think this goes into Firefox::File Handling.
Component: General → File Handling
OS: Unspecified → Linux
Product: Core → Firefox
sorry. missed a step 1. visit this link https://www.dailykos.com/stories/2007/12/31/428559/- 2. wait for a few seconds 3. click on file and then "save page as" 3a. make sure "web page, complete" is selected 4. enter y.html and hit return 5. wait for download to complete 6. check the download directory
I confirm the issue on Linux, during my test the download didn't complete. Since we don't have a team working on this area at the moment, it may be a while before the issue is fixed. As a workaround, you may try the "Save Page WE" add-on which will also save the page in a single file.
Priority: -- → P3
After further investigation, I have a way to produce the problem without the complexities of the dailykos.com site 1. create a simple HTML page as a local file and put <img src="https://images.splattt.com/d_dcat.jpg"></img> in it. (This link is a broken link) 2. visit the local file in firefox 3. wait for a few seconds 4. click on File in MenuBar and then "save page as" 5. make sure "web page, complete" is selected 6. enter y.html and hit return 7. wait for download to complete 8. check the download directory
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.