1829826 - Firefox keeps deleting downloaded PDF files in a private window after closing it

Status: RESOLVED DUPLICATE of bug 1790641

(Firefox :: File Handling, defect)

Description

[Przemysław Siekiera]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0

Steps to reproduce:

Video: https://www.youtube.com/watch?v=erg5ef6KGeE

Example steps to reproduce:

1. Launch Firefox and open a private window
2. Go to https://filesamples.com/formats/pdf, agree to the cookies and click on the Download button next to sample3.pdf file

Actual results:

If you didn't change the setting that decides what Firefox does with PDF files, the downloaded file should automatically open in a new [private] tab; also you should be able to find it (with the Read-only attribute set) in Windows' Downloads folder. Now when you exit the opened private window you should find that the downloaded PDF file got removed from the Downloads folder.

Expected results:

The downloaded PDF files shouldn't be deleted when you close the private browsing session (also don't add “Read-only” attribute to files [Since they are being saved to the Downloads folder, not the %Temp% folder]?).

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Firefox::PDF Viewer' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Rares Doghi, Desktop QA]

I was able to reproduce this issue as well, it seems that in older builds the file would be downloaded in a temp folder and directly opened in a new tab while now its being downloaded in the default Download folder and then deleted when the browser closes, which could be a little confusing for the users who see their files while the browser is opened and then can no longer find them once the browser is closed.

This is the pushlog from the regression range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=110862c2c4da9f9cb2b6ecc64668fac0b6275350&tochange=77e7d5bff788d193d37f486abe9a5eb1571ae540
It seems that bug 1772569 is whats causing this issue.

@Neil can you please take a look at this issue ? is this the intended behavior now ?