Actually reset the PDFPageProxy._xfaPromise
property as intended (PR 13069 follow-up)
#13119
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.
Similar to the existing
annotationsPromise
and_jsActionsPromise
properties, the new_xfaPromise
should obviously also be reset, since otherwise you might end up holding onto a lot of data for pages that are no longer active.(That caching wasn't present in the original version of PR #13069, which is why I didn't spot it until now.)