A couple of small image caching/sending improvements #11974
Merged
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.
Remove an unnecessary
RefSetCache.prototype.has()
call fromGlobalImageCache.getData
We can simply attempt to get the data directly, and instead check the result, rather than first checking if it exists.
Extract the actual sending of image data from the
PartialEvaluator.buildPaintImageXObject
methodAfter PRs Support (rare) Type3 fonts which contains image resources (issue 10717) #10727 and Attempt to cache repeated images at the document, rather than the page, level (issue 11878) #11912, the code responsible for sending the decoded image data to the main-thread has now become a fair bit more involved the previously.
To reduce the amount of duplication here, the actual code responsible for sending the data is thus extracted into a new helper method instead.