Skip to content

[Bug]: Regression in outline navigation #18408

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mrtcode opened this issue Jul 8, 2024 · 5 comments · Fixed by #18453
Closed

[Bug]: Regression in outline navigation #18408

mrtcode opened this issue Jul 8, 2024 · 5 comments · Fixed by #18453

Comments

@mrtcode
Copy link

mrtcode commented Jul 8, 2024

Attach (recommended) or Link to PDF file

Can’t provide an example due to copyright restrictions.

Web browser and its version

Chrome, Safari, Firefox

Operating system and its version

macOS

PDF.js version

4.5.47

Is the bug present in the latest PDF.js version?

Yes

Is a browser extension

No

Steps to reproduce the problem

Click on any outline item.

What is the expected behavior?

Navigate to desired destination.

What went wrong?

pdf_link_service.js:149 goToDestination: "null" is not a valid destination array, for dest="section*.5.2".
goToDestination @ pdf_link_service.js:149
await in goToDestination (async)
element.onclick @ pdf_outline_viewer.js:153

Link to a viewer

No response

Additional context

This seems to be a regression because it works as expected in PDF.js 3.7.96 and all other PDF viewers, but not in PDF.js 4.5.47.

Hopefully, the error message is enough to isolate the problem, but if not, you can contact me for the file.

@wikisqueaks
Copy link

I am also experiencing this behaviour.

@timvandermeij
Copy link
Contributor

timvandermeij commented Jul 10, 2024

Unfortunately the PDF file is a required part of the issue template because we can't debug the issue with just the error message, and PDF files need to be attached to the issue so everything is in one place and everyone from the community can help out without having to contact the issue reporter first. Therefore, please either provide a non-copyrighted file or create a new PDF file without copyrighted content that triggers the issue.

@timvandermeij
Copy link
Contributor

timvandermeij commented Jul 13, 2024

Closing due to the above. The issue can be reopened if a publicly available PDF file that shows the issue is attached.

@mrtcode
Copy link
Author

mrtcode commented Jul 14, 2024

All right, I found an open-access book with the same problem:

https://link.springer.com/content/pdf/10.1007/978-3-319-93935-3.pdf

@mrtcode
Copy link
Author

mrtcode commented Jul 17, 2024

Can the issue be reopened now that I have provided the file?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants