This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Etsi tuesta

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Lue lisää

toolbar download item: open a file from list don't use related application

more options

Hi I'm using FF 62 on Ubuntu desktop 16.04 64bit when I download a file the button "Icon down" in the toolbar became blue. clicking on it open a list of downloaded files. clicking on a file on the list, not open the file with his related application. example: I download a pdf, then clicking on it open vscode !! If I open the download page from "history, bookmark etc" toolbar button and I click on a pdf file to open it, the file open in Document Viewer as expected. what I can do to fix ?

Hi I'm using FF 62 on Ubuntu desktop 16.04 64bit when I download a file the button "Icon down" in the toolbar became blue. clicking on it open a list of downloaded files. clicking on a file on the list, not open the file with his related application. example: I download a pdf, then clicking on it open vscode !! If I open the download page from "history, bookmark etc" toolbar button and I click on a pdf file to open it, the file open in Document Viewer as expected. what I can do to fix ?

Kaikki vastaukset (1)

more options

When you open a saved file from the Downloads panel, Firefox usually looks to your OS-level association for the content. If the file has a .pdf extension on the name, that normally would be some kind of PDF reader and not VSCode. But some sites may not send a full file name, or Firefox might save under a script name such as pushpdf.php in which case it would make more sense that it opens in VSCode.

When you open content from a link in a page, Firefox takes its cue from the Content-Type header sent with the content instead of from the file extension. So if the site sends application/pdf Firefox will, by default, use the built-in PDF viewer regardless of whether it's a .pdf, .jsp, etc.