jumpToAnnotation(annotation [, options]) is not allowing smooth scrolling

WebViewer Version: 11

Do you have an issue with a specific file(s)? No, all files
Can you reproduce using one of our samples or online demos? It is happening in code.
Are you using the WebViewer server?
Does the issue only happen on certain browsers? All browsers
Is your issue related to a front-end framework? Yes, using it with Next JS
Is your issue related to annotations? Yes

Please give a summary of your issue:
I am trying to implement the scroll feature in pdf, using jumpToAnnotation works, but the transition is so rapid. Using one of the optional parameter isSmoothScroll, is also not working; the documentation mentions that if this is set to true, the viewer should move to the annotation smoothly.

Documentation link: Apryse WebViewer Class: AnnotationManager

Please describe your issue and provide steps to reproduce it: Try implementing scroll functionality using the jumpToAnnotation function.

Please provide a link to a minimal sample where the issue is reproducible: NA, used in production code.

Hello, I’m AiRon, an automated tech support bot :robot:
While you wait for one of our customer support representatives, I can help you with your question.


It seems you’re facing an issue with the jumpToAnnotation method in Apryse’s WebViewer, where the isSmoothScroll option does not produce the expected smooth scrolling effect. This could be due to the integration specifics with Next.js or the way the jumpToAnnotation function is being called.

Some things you can try:

  • Ensure that the isSmoothScroll option is explicitly set to true when calling jumpToAnnotation.

  • Check if there are any CSS styles or JavaScript code in your application that might interfere with the scrolling behavior, such as custom scroll settings or event listeners.

  • Verify that the WebViewer version you are using supports the isSmoothScroll option. Although you mentioned using version 11, ensure there are no discrepancies in your setup.

  • Test the functionality in a minimal setup outside of Next.js to see if the issue is specifically related to the Next.js environment.



Here are some resources that might help you:


Hopefully, this helps you solve your problem while you wait for a human to get back to you.

Hello @pushpam.priyaa,

Thank you for posting on our forum.

After some initial investigation, I found our Development team is aware of this issue and it is currently raised to our backlog for our Product team to review. From our findings it looks like this issue originally started occurring in Version 11.9 and is not present in Version 11.8. Let us know if this is consistent with your findings.

We do not have a firm timeline at this moment when the issue will be worked on, but we will be sure to reach out if we have an update to provide.

Thank you for bringing this to our attention.

Best Regards,
Jacob Romano Carlsen
Web Development Support Engineer
Apryse Software Inc.