Phillip Jones wrote:
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?
I don't think it necessarily is supposed to. On occasion, when SeaMonkey
crashes for whatever reason it goes to a Blank Home page the only way to
cure is go to your homepage. then go to Preferences (in Macintosh -
called something else in Widows/Linux/UNIX) then To Browser clear out
what ever you have set as home page and click on Use current page) this
will fix it until next crash. Possibly the same mechanism the screws up
then is screwing up when you call a PDF and the only PDF viewer from
within SM or ThunderBird for that matter, that works is called PDF
Browser Plugin by Schubert of Germany.
There's no crash involved with this, though - it's just this extra,
blank page that opens up while the PDF is downloading and before
whatever external PDF reader is called, and which stays open and blank,
even after the PDF reader is exited.
It's not a crash, and it's really only "cumbersome" to the extent that
it requires one click on the "X" to close it away, but it's still a bug.
-JW
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
