Access navigator
safely in the src/display/annotation_layer.js
file
#13801
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.
For code that's part of the core library, rather than e.g. the
web/
-folder, we should always be careful about directly accessing any DOM methods.The
navigator
is one such structure, which shouldn't be assumed to always be available and we should thus check that it's actually present.[1]Hence this patch re-factors the
navigator.platform
access, in theAnnotationLayer
-code, to ensure that it's generally safe. Furthermore, to reduce unnecessary repeated string-matching to determine the current platform, we're now using a shadowed getter which is evaluated only once instead (at first access).[1] Note e.g. the
isSyncFontLoadingSupported
getter, in thesrc/display/font_loader.js
file.