Handle large (1000+ page) documents better
Open
enhancement
- Dominant language
- JavaScript
- Stars
- 333
- Forks
- 98
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we generate the DOM objects for all pages at init, but we could be smarter about loading only a small subset of these pages, then adding more (and removing some) as necessary.
Contributor guide
Research direction
Start by tracing the initialization path that creates DOM objects for every page and identify where page loading and removal can be controlled. Compare behavior on a document exceeding 1,000 pages, then define completion as keeping only a small needed subset in the DOM while adding and removing pages as navigation requires.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100