On 4/6/10 8:37 AM, Arne wrote: > David E. Ross wrote: >> On 4/6/10 2:40 AM, Arne wrote: >>> David E. Ross wrote: >>>> On 4/5/10 9:14 AM, Walter wrote: >>>>> I click on a pdf file and adobe reader loads it ok. directly behind it >>>>> is a blank page. shouldn't it be the page from which I came? with the >>>>> link to the pdf page? >>>>> Walter. >>>> >>>> I get this sometimes when the link is actually for JavaScript. The >>>> script tries to launch a new page (which in my case becomes a new tab) >>>> as it fetches the PDF file. It seems that the script actually downloads >>>> another script (new page) that, in turn, gets the PDF file. Obviously, >>>> if this is what is happening, it's a poorly designed Web site. >>> >>> In my opinion there is no need at all for SM to open a blank tab/page >>> when it's the PDF reader that is launched, no matter how the web page >>> is designed! Why not just open the PDF reader? >>> >> >> It's not the launching of the PDF reader that throws up the blank page. >> It's the JavaScript that thinks the PDF file will be viewed in a >> browser window. However, the PDF file is served by a MIME type that >> instead requires a separate PDF reader. As I said before, it's the >> result of a poorly designed Web page. > > Okay, then give me a link to a site with downloadable PDF-files where > this don't happen. Sure there must be at least one you have found, and > even that would be one more than I know about. > > I have also still to find a PDF file that *requires* a separate PDF > reader. Only in IE (v.8) I have no clue how to prevent PDF's from > opening within the browser window, but since I don't use IE I don't > care. ;) > > I believe it is the code within SM that cause this, not the site. When > SM can't decide if the pref settings are set to open within the SM > tab/page or within the stand alone PDF reader. >
Go to my <http://www.rossde.com/garden/public_gardens.html>. Scroll down to "Hampton Court Palace, Surrey, England, UK". Select the link "gardens" in the phrase "we found the formal gardens". For SeaMonkey 2.0.4, this PDF file opens within my browser using the Adobe Reader plugin nppdf32.dll. Besides the JavaScript situation, other causes of this opening in Adobe Reader itself are: * You are missing the plugin. On the SeaMonkey menu bar, select [Help > About Plugins]. On the resulting page, check to make sure that you see nppdf32.dll. * The PDF file is being incorrectly served by the Web server. It should be served as application/pdf. In my setup, a PDF file served as application/x-pdf will instead open in Adobe Reader itself; I'm not sure of why there is a distinction. You can see how a link is served if you have the LiveHTTPHeaders extension installed in SeaMonkey. * Your setup requests PDF files to be opened in Adobe Reader itself. To see what your setup is for this, select [Edit > Preferences] on the SeaMonkey menu bar. On the left side of the Preferences window, under "Category", select [Browser > Helper Applications]. The Helper Applications pane may show several entries for Adobe; to see the differences in these entries, either stretch the window horizontally or place your cursor over an entry to get a tooltip. In my setup, there are six entries: four of them result in opening the file within SeaMonkey, one results in opening the file in Adobe Reader itself, and one asks the user how the file is to be handled. Three depend on the file-type indicated by the file extension, and three depend on how the file is served. -- David E. Ross <http://www.rossde.com/> Go to Mozdev at <http://www.mozdev.org/> for quick access to extensions for Firefox, Thunderbird, SeaMonkey, and other Mozilla-related applications. You can access Mozdev much more quickly than you can Mozilla Add-Ons. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
