Tweak PDFPageView
to reflect that this.annotationLayer
is an AnnotationsLayerBuilder
instance, instead of a DOM element (PR 5552 follow-up)
#6475
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.
In PR #5552, specifically commit 9f384bb, the meaning of
this.annotationLayer
changed inPDFPageView
. Previously it referred directly to a DOM element, but now it's instead an instance ofAnnotationsLayerBuilder
.This patch tweaks things so that we won't try to hide a non-existent
annotationLayer
div inPDFPageView_reset
, and also so that we don't attempt to insert empty (null
) DOM elements inPDFPageView_draw
.