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.

Search Support

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.

Learn More

Natao arisiva ity resaka mitohy ity. Mametraha fanontaniana azafady raha mila fanampiana.

PDF download from Tab "bar" creates damaged file..."Save Page As.." WORKS

  • 1 valiny
  • 2 manana an'ity olana ity
  • 10 views
  • Valiny farany nomen'i philipp

more options

Using Firefox 25.0 Yahoo Edition yahoo! 1.24. When I access a website that creates a .pdf , I can VIEW the file just fine in the Tab window...but when I used the "download" icon (upper right menu bar), the file that is created on my iMac, my Win7PC, my Win8 laptop and/or my old winXP cannot be viewed with Adobe XI...it says the file is "damaged".

HOWEVER, when I use the "Save Page As" option (instead of the Tab's "download" icon) ... the downloaded file works just fine with Adobe XI.

Would seem to be a bug???

Using Firefox 25.0 Yahoo Edition yahoo! 1.24. When I access a website that creates a .pdf , I can VIEW the file just fine in the Tab window...but when I used the "download" icon (upper right menu bar), the file that is created on my iMac, my Win7PC, my Win8 laptop and/or my old winXP cannot be viewed with Adobe XI...it says the file is "damaged". HOWEVER, when I use the "Save Page As" option (instead of the Tab's "download" icon) ... the downloaded file works just fine with Adobe XI. Would seem to be a bug???

Vahaolana nofidina

hello finnsoft2, can you try if you can replicate the issue with firefox 26 beta from mozilla.org/beta ? it should contain a fix for this issue already...

Hamaky an'ity valiny ity @ sehatra 👍 2

All Replies (1)

more options

Vahaolana Nofidina

hello finnsoft2, can you try if you can replicate the issue with firefox 26 beta from mozilla.org/beta ? it should contain a fix for this issue already...