Access the XRef
/Catalog
data correctly in the "GetStats"/"GetPageIndex" handlers in src/core/worker.js
#12276
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.
Access the
XRef
data correctly in the "GetStats" handler insrc/core/worker.js
Even though the code obviously works as-is, given that we have unit-tests for it, it still feels incorrect to just assume that the
XRef
-instance has all of its properties immediately available. Especially when (almost) all of the other handlers, insrc/core/worker.js
, protect their data accesses with appropriatepdfManager.ensure
calls.Access the
Catalog
data correctly in the "GetPageIndex" handler insrc/core/worker.js
Even though the code obviously works as-is, given that we have unit-tests for it, it still feels incorrect to just assume that the
Catalog
-instance has all of its properties immediately available. Especially when (almost) all of the other handlers, insrc/core/worker.js
, protect their data accesses with appropriatepdfManager.ensure
calls.