270328 - PDF fragment identifiers don't work

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[John Pye]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a4) Gecko/20040927
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a4) Gecko/20040927

Fragment identifiers from PDF URLs should be passed to the acrobat viewer.

In my system, which which has Acrobat Reader v 4.0 installed, this doesn't happen.

It happens fine in Internet Explorer, but IE is opening the PDF inside the IE
window, Moz is opening the PDF in an Acrobat window (which is how I like it)



Reproducible: Always
Steps to Reproduce:
1. Click http://www.iapws.org/relguide/visc.pdf#page=7

Actual Results:  
PDF file opens to first page

Expected Results:  
PDF should open and jump to page 7.

I don't know what the mechanism is by which Acrobat is invoked but I know that
you can pass a desired bookmark in via the command line.

Comment 1

[Boris Zbarsky [:bzbarsky]]

We invoke Acrobat on a local file with the saved data.  We can't really pass
random chunks of the original URI at that point, because they have nothing to do
with the new file location...

Comment 2

[Christian :Biesinger (don't email me, ping me on IRC)]

I'm sure I've seen this before, but I can't find it currently...

Comment 3

[John Pye]

FYI I checked it with Moz 1.7.3 and Acrobat Reader 6.0 on Win XP, with Acrobat
functioning as a browser plugin, and it works ok.

If you are opening Acrobat as a file handler for a local file, maybe you could
use some way of specifying the page to view via the commandline, eg /page=7 or
something like that (I haven't found anything in the acrobat docs)

Comment 4

[Boris Zbarsky [:bzbarsky]]

You know as much as we do about Acrobat.  If there's a way to send such
information to it, I'm not aware of it.

Comment 5

[John Pye]

So if it were possible to specify the page that should be opened when launching
Acrobat as a external app, would that be something you could integrate into the
acrobat launcher, or would such a thing kinda go outside your standard
helper-application implementation and not really be feasible?

I don't know how many people have Acrobat set up like this, but I got tired of
all the bells and whistles of the newest version of Acrobat, and so have been
using Acrobat 4, which works best as an external program - not even sure if it
works as a browser plugin.

Is this page= thing an issue with Linux too, I wonder? Does acroread (any
version) run as a browser plugin or only ever as an external program?

Comment 6

[Boris Zbarsky [:bzbarsky]]

It wouldn't fit into our app-launching behavior too well, no... depending on
what was involved and whether it used a setup shared by other apps we might be
tempted to support it.

As for plugins, the nppdf plugin (using the same core as acroread) has been
working fine on Linux for years...

Comment 7

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 8

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.