108464 - adobe reader and large pdf files

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[john russell]

the example document is the guide to canadian tax form 
for 2000.  it is 216k long.  when i attempt to load it
it seems to launge adobe reader 5 ok, but the screen
remains blank after download. When i press the back button
the document appears briefly, then is covered up by the
previous page. This action occurs in other gecko engine
based browsers such as netscape 6.2 and K-meleon .6
Netscape 4.7, Opera 5.12 and msie 6.0  have no problem
with the page.  Smaller pdf files from the same site
are ok with gecko browsers....  Is there a workaround
or is this something new that will be triaged.
An even longer file at www.geocities.com/tmason1/tmp.htm
(1.2 meg) is also a no go -- and even net4.7 fails on that
large a file  but not opera or msie.  Any suggestions as
to work around ???

Comment 1

[Itamar]

I have 
Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.5) Gecko/20011011
and Adobe reader 4.05ME
works fine here

Comment 2

[Andrew Hagen]

WFM  Mozilla 0.9.5+
Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.5+) Gecko/20011113, Acrobat Reader
5.0.

Reporter, could you open Acrobat Reader 5.0, go to Edit | Preferences | Update,
hit "update Acrobat now" and see if you have all the updates? If not, please
download them. Does that solve the problem?

If your problem continues, could you please provide the Mozilla version you are
using? That's available in Mozilla from Help | about Mozilla.

Comment 3

[Andrew Hagen]

The reporter has told me that he has fixed the problem in private e-mail:

> >I found a solution that worked by going into Acrobat Reader 5.0 and
> >deselecting the preference -- option -- display pdf in browser line.
> >By letting the browser use Acrobat in helper mode there seemed to
> >be enough buffer space available for pdf files reater than a meg.
> >Before that option was deselected, there were problems.
> >Unfortunately this option was selected as the out-of-the-box
> >config of Adobe -- so it is their problem, not mozilla's
> >mozilla build 2001 10 22 03

I'm closing this bug.