(In reply to :Gijs (he/him) from bug 1790641 comment #28) > If you feel strongly that we should differentiate between those two "download" hints from the website, you can file a separate bug - it's orthogonal to the private window issue that this bug is about. I don't see us wholesale reverting bug 453455. To be clear, I do not want such behavior. > It otherwise works for `txt` only because that is a mimetype (`text/plain`) that the browser can render natively. It "works" for all such types, but no other ones. As a result, it doesn't work for PDF because that's rendered by PDF.js, not the browser (it's not treated the same as HTML/txt/images/media which the browser can render itself). So it's less that we did something different for PDF, and more that we [still] treat PDF like "all the other files" in this respect. It is an implementation detail. From users perspective, Firefox can render PDF in the browser tab just like native file types. In Settings > General > Applications, PDF has the "Open in Firefox" choice just like native file types. But the behavior of the option is different from other native types, different from Chrome. It is counterintuitive IMO. > Yes, it would potentially help some users with this issue as regards PDFs, but would not help for any other filetypes and would not help cases where the website choice ("download" vs "show") isn't the one the user wants. No other external file types has the "Open in Firefox" option. Since we dropped support for third-party plug-ins, only PDF is special.
Bug 1811830 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to :Gijs (he/him) from bug 1790641 comment #28) > If you feel strongly that we should differentiate between those two "download" hints from the website, you can file a separate bug - it's orthogonal to the private window issue that this bug is about. I don't see us wholesale reverting bug 453455. To be clear, I do not want such behavior. > It otherwise works for `txt` only because that is a mimetype (`text/plain`) that the browser can render natively. It "works" for all such types, but no other ones. As a result, it doesn't work for PDF because that's rendered by PDF.js, not the browser (it's not treated the same as HTML/txt/images/media which the browser can render itself). So it's less that we did something different for PDF, and more that we [still] treat PDF like "all the other files" in this respect. It is an implementation detail. From users perspective, Firefox can render PDF in the browser tab just like native file types. In Settings > General > Applications, PDF has the "Open in Firefox" choice just like native file types. But the behavior of the option is different from other native types, different from Chrome. It is counterintuitive IMO. > Yes, it would potentially help some users with this issue as regards PDFs, but would not help for any other filetypes and would not help cases where the website choice ("download" vs "show") isn't the one the user wants. No other external file types have the "Open in Firefox" option. Since we dropped support for third-party plug-ins, only PDF is special.