-
-
Notifications
You must be signed in to change notification settings - Fork 916
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
Improvement: Preload Pages and Cache loaded pages #1816
Comments
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 14 days. |
@wojtekmaj how can a Feature Request get stale? :) |
I guess you could make a proxy component like OffscreenPage by rendering Page component, with text and annotation layers turned off, and customRenderer noop function? 🤔 You also have useDocumentContext hook which enables you to programatically get pages as you need. |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 14 days. |
So I guess this is nothing which could be added directly to this library then? :) |
Before you start - checklist
Description
I just integrated this library in my App and it’s a huge upgrade compared to an iframe from a visual perspective. However, talking about performance it cannot compete with an iframe. And that is totally ok, though I was wondering if it would be possible in a future version to automatically preload the next page and keep the previous few pages in memory maybe? Because changing pages really takes some time and even when you go back to pages previously rendered they need to load again (without even showing the loading indicator and just being white).
Proposed solution
Automatically preload the next (or even next few) pages.
Keep previous few pages in Memory. Also preload the previous page if not in memory already.
Thank you!!
The text was updated successfully, but these errors were encountered: