[
https://issues.apache.org/jira/browse/FOP-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472835#comment-17472835
]
Chris Bowditch edited comment on FOP-2839 at 1/11/22, 3:45 PM:
---------------------------------------------------------------
I have seen the same thing when using Acrobat Reader DC, but Chrome PDF Viewer
seems to work fine, so seems to be a quirk with Acrobat Reader
was (Author: cbowditch):
I have seen the same thing when using Acrobat Reader DC, bt Chrome PDF Viewer
seems to work fine, so seems to be a quirk with Acrobat Reader
> FOP Extensions: Named destination link not working
> --------------------------------------------------
>
> Key: FOP-2839
> URL: https://issues.apache.org/jira/browse/FOP-2839
> Project: FOP
> Issue Type: Bug
> Components: unqualified
> Affects Versions: 2.2, 2.6
> Environment: Windows 10
> Reporter: Nadine Ausländer
> Priority: Major
> Attachments: sourceDoc.fo, targetDoc.fo
>
>
> h3. Summary
> Given is a link from Doc A to a named destination in Doc B. Since FOP 2.2 a
> fox:destination in Doc B does not work anymore as the link target in PDF
> output using Adobe Acrobat Reader DC. Same issue observed in FOP 2.3.
> h3. Observed behavior
> When following the link in Doc A, the first page of Doc B is displayed.
> h3. Expected behavior
> When following the link in Doc A, Doc B is opened at the named destination.
> h3. Test documents
> Test documents also attached.
> Doc A: sourceDoc.fo:
> {code:java}
> <fo:basic-link
> show-destination="new" text-decoration="underline"
> color="#0099D4"
> external-destination="url(targetDoc.pdf#dest=target)">
> Link to external PDF with anchor
> </fo:basic-link>
> {code}
> Doc B: targetDoc.fo
> {code:java}
> <fo:block id="target"><fox:destination internal-destination="target"/>Target
> Anchor</fo:block>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
