53344 - PDF Support Problem: NPP_NewStream Never Sets the Stream as Seekable

Status: VERIFIED DUPLICATE of bug 32319

(Core Graveyard :: Plug-ins, defect, P2)

Description

[lmcquarr]

Using the M17 Build  (windows)
(latest build is totally broken with respect to PDF, so needed to go back
to M17), mozilla never tells us that the stream is seekable in NPP_NewStream.

This is a real problem with PDF files.  We need seekable streams with
PDF to do byte range requests for parts of the PDF file that we need.
In the current state of mozilla, the entire PDF file is downloaded before
anything at all is displayed.  Many PDF files are quite large!
To require that the entire PDF file be downloaded makes it unusable.
Much engineering work was done by Adobe and Netscape to support
seekable streams and byte range requests for previous versions
of Navigator (and IE).

*** Without seekable streams in Mozilla, it will be a very bad platform for PDF
and Acrobat usage ***

In order to continue my testing, I am going to modify the Acrobat plug-in
to pretend that Mozilla told us the stream was seekable and see what
happens when I start issuing byte range requests.  I am sure I will
find more bugs since Acrobat is one of the few plug-ins to use this
feature  (and use it we must!).


BTW -- I am fairly sure I entered this bug at the beginning of this year.
Due to a hard disk crash, however, I cannot easily produce a bug number.

Comment 1

[lmcquarr]

Now that 53122 is fixed, I can use today's build.   This bug still happens.

Comment 2

[sean echevarria]

related to bug 32319?

Comment 3

[ekrock's old account (dead)]

*** This bug has been marked as a duplicate of 32319 ***

Comment 4

[Stephen Walker]

verified