Harden DOCX cache and reader backends - #19
Merged
Conversation
dowellhz
marked this pull request as ready for review
August 14, 2026 04:54
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
The existing DOCX cache still extracted the complete archive, serialized all builders behind a global lock, and enforced only an entry-count limit. Navigation and zoom commands also coupled shared controller behavior directly to PDFKit and WebKit.
Validation
./tests/run.sh./scripts/check.sh --no-build./scripts/check_ui_theme.sh --warnings-as-errors./scripts/build_app.shgit diff --check