User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 I installed Adobe Reader 8. After installing the program and browsing the web, whenever I encountered a href tag pointing to a pdf file (see example url provided), clicking on the link just downloaded the pdf to my desktop (no download notification, no save dialog, the new tab would flash for a second then close). My setting are configured to open in a new tab. I tried all of the options in Tools->Options->Downloads and couldn't get the pdf's to open in a new tab. I uninstalled Adobe Reader 8 and rolled back to Adobe Professional 7.0.8. Tried the same links again in Firefox, the expected behavior worked, clicking on href's to pdf's opened the pdf in a new tab. Everything works fine in IE7. Clicking on PDF's with Adobe 8 installed opened the PDF in a new browser window. I'm guessing that this is an Adobe issue, just thought you should be aware of the issue that we are experiencing. Reproducible: Always Steps to Reproduce: 1.Install Adobe Reader 8 2.Browse to provided URL 3.Click on PDF link in the body of the web page 4.If nothing happens, look on your desktop for the file Actual Results: The PDF files were downloaded to my desktop, with no warning and without opening in a new tab. Expected Results: The PDF should have opened in a new tab.
WFM using Minefield and Reader 8, with a clean profile/no extensions. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061207 Minefield/3.0a1 Firefox ID:2006120704 [cairo]
Today I installed Adobe Reader 8 with Firefox 184.108.40.206 <http://220.127.116.11>. None of the behaviors as reported in my ticket occurred. Everything worked as I expected. Thanks again.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
-> worksforme (Fixed mean in bugzilla that a code change happened like a patch or so)
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.