Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

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

  • 1 antwoord
  • 2 hierdie probleem
  • 10 views
  • Laaste antwoord deur 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???

Gekose oplossing

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...

Lees dié antwoord in konteks 👍 2

All Replies (1)

more options

Gekose oplossing

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...