Alot depends on where your downloading from? So what is the site the file is downloaded from? And it could be how the site is formatting the file so that if it is a pdf it could look like this *.pdf.adobe that is what is saved and you will have to change it from *.pdf.adobe to *.pdf so it will switch to the right format. But as I said it's not a browser but a site that does that.

Thanks WestEnd, The biggest offender seems to be Fedex. We download our daily logs/reports (*.xlsx) or (*.pdf) of package shipments. When FF downloads the file they are in my download folder without an extension at all. Once I rename them with the *.xlsx or *.pdf extension they seem to work. What is funny is that media files seem to work just fine. I will send an inquiry to Fedex and see if they can shed some light. Thanks for your reply. Much appreciated.

This is mostly like due to some kinda protection on their site to prevent malware from detecting and infecting extensions.

Just wanted to share further info. Have done specific tests this morning using FF, Chrome and Edge (latest updates). Chrome and Edge were able to handle the download with the extensions in place in their default state. FF exhibited the continued same behavior (no extension).

However, when I went in and did a custom search (different file name) and then downloaded the results FF handled the download with the proper extension. This leads me to believe that their is something in the string that passes the default report to FF that it does not interpret as a specific type of document. To further support that I noticed that when FF had a problem with the download the file name was truncated. This makes me think that there is something (formatting, character, space...?) in the default file name format that FF just does not like.

Don't have a lot more time to troubleshoot this today. However, perhaps another person that has this or similar issue may be able to take this and discover more.

Thanks for your input!