Improve the PDFViewerApplication._contentLength
handling in the viewer, related mostly to scripting
#12822
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.
Ensure that
PDFViewerApplication._contentLength
is always updated with the correct length, as returned byPDFDocumentProxy.getDownloadInfo
, and only let thePDFViewerApplication._initializeMetadata
method overwrite if it's not already been set.Finally, in
PDFViewerApplication._initializeJavaScript
, the fallback_contentLength
handling is now moved to just after the fallbackdocumentInfo
handling, such that all the fallback code is in one place within the method.