Can we update the note panel functionality so it can load the annotation in chunk or on scroll

Technical Support WebViewer
, , ,
1

WebViewer Version: 11.7.2

Do you have an issue with a specific file(s)? No
Can you reproduce using one of our samples or online demos? No
Are you using the WebViewer server? No
Does the issue only happen on certain browsers? No
Is your issue related to a front-end framework? No
Is your issue related to annotations? No

Please give a brief summary of your issue:
Can we update the note panel functionality so it can load the annotation in chunk or on scroll

Please describe your issue and provide steps to reproduce it:

Background / Current Behavior

In our application, we are using Apryse WebViewer with a document that can contain a very large number of annotations (thousands in some cases).

Currently, the Notes Panel loads all annotations at once when:

  • The document finishes loading, or
  • The Notes Panel is opened

This causes the following issues:

  • Significant UI lag / freezing when large annotation sets exist
  • High memory usage in the browser
  • Slow initial render of the Notes Panel
  • Poor user experience for documents with long annotation histories

Observed Limitation

From our investigation:

  • The Notes Panel internally renders the full annotation list eagerly
  • There is no built-in pagination, chunking, or virtualized rendering
  • The annotation list grows linearly and becomes expensive to render

Even if annotations are already imported efficiently, the Notes Panel UI rendering becomes the bottleneck.

Requested Enhancement

We would like to know if it is possible to update or extend the Notes Panel behavior so that annotations can be loaded:

:one: In Chunks (Pagination)

  • Load an initial batch (e.g. 50–100 annotations)
  • Load the next batch only when requested (scroll / pagination / API call)

:two: On Scroll (Lazy / Virtualized Rendering)

  • Render only the annotations that are currently visible
  • Load additional annotations when the user scrolls down
  • Similar to “infinite scroll” or virtual list behavior

Why This Is Needed

Performance Benefits

  • Faster Notes Panel opening
  • Reduced DOM size
  • Lower memory usage
  • Smooth scrolling experience

UX Benefits

  • No freezing when documents contain thousands of annotations
  • Faster access to recent annotations
  • Scales well for enterprise-level documents
    image
    image363Ă—753 8.45 KB

Please provide a link to a minimal sample where the issue is reproducible:

2

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 like you’re experiencing performance issues with the Notes Panel when handling a large number of annotations in WebViewer. Unfortunately, as of the current capabilities, WebViewer does not natively support loading annotations in chunks or implementing lazy loading (virtualized rendering) directly within the Notes Panel. However, you can try some workarounds to improve performance.

Some things you can try:

  • Implement a custom Notes Panel: Create a custom component that fetches and displays annotations in chunks or uses a virtual scrolling mechanism.

  • Use the setCustomNoteFilter: This API allows you to filter which annotations are displayed in the Notes Panel. Although it won’t help with lazy loading, it can reduce the number of annotations shown initially.

  • Optimize annotation data handling: Ensure that only necessary annotation data is kept in memory, and consider using efficient data structures or storage mechanisms.




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.

1 Like
4

Hi there,

Currently, the notesPanel does not have the capabilities you listed, but we could create a request to the backlog for our product team to review for feasibility and viability.

The workaround for now would be to create a custom panel via our modular UI or forking our UI:

If you could provide some further information about the context of your request. We would be interested to know:

  • What is the workflow in which you would use the requested feature?
  • Why is the feature valuable to you and your users?
  • How are you coping without it right now?

best regards,
Kevin

1 Like