Privacy leak/broken PDF-setup in private browsing mode
Categories
(Firefox :: File Handling, defect)
Tracking
()
People
(Reporter: sworddragon2, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0
Steps to reproduce:
- Enable permanent private browsing mode
- Open a PDF from the web for example https://cdn.discordapp.com/attachments/712712343393533999/813101874382504037/arcade.pdf
Actual results:
Firefox asks what to do with the PDF despite opening it in Firefox being the default. Even selecting to open the PDF now with Firefox and enabling the checkbox to make this action the default does still cause asking via this popup what to do with the PDF on the next try again. Additionally the PDF is stored and viewed from the user's temporary folder while there was no initial feedback that this would happen causing a privacy breach.
Expected results:
At least Firefox should give feedback that opening the PDF causes a privacy leak here or to not allow to do this action at all. But since there is no strict technical limitation why Firefox can't handle the PDF in-memory as it already does with most other storage actions this is probably the real longterm-solution - as in the STR the PDF would then simply open without the popup and no privacy leak would occur.
|
||
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::PDF Viewer' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Updated•3 years ago
|
|
||
Comment 2•3 years ago
|
||
We don't open in the viewer because the server sends content-disposition: attachment, which is bug 453455. We're hoping to fix that "soon" (see the very last comment, yes, after some 15 years there is active work underway, please be patient).
Otherwise, this is no different from 1546969 and so I don't think it makes sense to keep a separate report open for PDFs.
Description
•