Cruz, Jaime ha scritto:
David E. Ross wrote:
On 6/23/11 6:53 PM, Cecil Bankston wrote:
David E. Ross wrote:
On 6/23/11 11:19 AM, Cecil Bankston wrote:
When I click a link for a PDF file in SeaMonkey 2.1 a new tab opens
with
the name of the file but the tab is blank. Previously such PDF files
would open normally in the browser. It made no difference whether I
had
Foxit or Adobe Reader set as my default PDF reader.
SeaMonkey 2.1 with Adobe Reader 10.1.0 on Windows XP SP3.
No problem.
If the link does not force a new tab or window and I do not
middle-click
to create a new tab, the PDF file opens in the existing tab. For a
short while, I get a blank screen with an ugly, large progress bar
(black frame with blue progress). When the document is open and
displayed, an Adobe Reader toolbar is superimposed over the window;
this
is easily and quickly dismissed.
I suggest you check your Adobe Reader preferences and then you
SeaMonkey
preferences.
Using the same OS and SeaMonkey& Adobe Reader versions, I just get a
blank tab. I don't see any SeaMonkey preferences that should be
relevant. SeaMonkey already is set to use the default PDF reader. PDF
attachments to e-mails also try to open in a browser tab but only
produce a blank tab.
Are you able to view a local PDF document that is on your own hard drive?
I've been seeing the same behavior. I have to download the PDF to my
hard drive and open it from there (yes, that works) because it seems to
refuse to open in Seamonkey. This was not a problem with 2.0.14. Another
work-around is switching to the IE rendering engine via IETab. Something
in the new Seamonkey is "broken."
I see this at home with XP SP3, and Acrobat X and at the office with XP
SP3 and Acrobat 9.
I've been having the same problem on linux (Kubuntu 11.04; 64 bit;
Acrobat 9.4; SM 2.1 and 2.2beta). I've noticed that it usually happened
(but it was quite random, generally) when I first opened some pdf; then
closed it and opened (the same or another) pdf later.
From System monitor I could see acroread was still running as zombie,
and plugin container was still active, even after closing all pdf
documents. Might that be related to the issue?
Now, I'm using evince through mozplugger, and it appears to work fine
--
Francesco
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
