Clicking link to PDFs to open them in PDF viewer now tends to put them in your Downloads directory rather than the /tmp one
Categories
(Firefox :: File Handling, defect)
Tracking
()
People
(Reporter: clement.lefevre, Unassigned)
Details
For some time now, it seems that on several occasions clicking a PDF link to open it in Firefox' PDF viewer downloads the file to ~/Downloads rather than in your tmp as it used to.
This creates files that stays there for no reason, like if Firefox would put its temporary files there too.
The file also appears there with a lock and a permissions set of 400.
|
||
Updated•1 year ago
|
|
||
Comment 1•1 year ago
|
||
This changed ages ago (for all files, not just PDFs), in Firefox 98. There's an about:config option added through bug 1738574 if you need the previous behaviour, but for reasons that are pretty exhaustively discussed there, it is no longer the default and I wouldn't personally recommend it.
There are also options to not download the file at all in this case (browser.download.open_pdf_attachments_inline) or to only download and not open, if the website indicates it is a download (browser.download.force_save_internally_handled_attachments).
We can't make everybody (anybody?!) happy here, as is obvious from the fact that bug 1883104 was filed a mere 3 days before this one... :-(
|
|
||
Comment 2•1 year ago
|
||
oh, and bug 1790641 and its many dupes complain that we do delete such PDFs in private browsing...
|
Reporter | |
Comment 3•1 year ago
•
|
||
(In reply to :Gijs (he/him) from comment #1)
This changed ages ago (for all files, not just PDFs), in Firefox 98. There's an about:config option added through bug 1738574 if you need the previous behaviour, but for reasons that are pretty exhaustively discussed there, it is no longer the default and I wouldn't personally recommend it.
I'd be curious as the which are the rationales behind the "I wouldn't personally recommend it."
I went on a quick look through https://bugzilla.mozilla.org/show_bug.cgi?id=1738574 (before seeing you provided two (other ones) right after…) to find the corresponding about:config, but I'm not even sure this is limited to PDFs (as those are opened by Firefox itself) or to much more things?
We can't make everybody (anybody?!) happy here, as is obvious from the fact that bug 1883104 was filed a mere 3 days before this one... :-(
Well yeah, of course, but that's especially true when people were used to a specific behavior for like more than 15 years and don't understand the reason that lead to this change, which is, at least for me, makes less sense. But I guess the answer to this would be the same as the answer to my first sentence and should be digged out from whichever bug introduced that change?
Description
•