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