Update the Annotation --zoom-factor CSS variable when PDFPageView is used standalone (PR 13868 follow-up)
#13874
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… is used standalone (PR 13868 follow-up) Without this patch, when using `PDFPageView` directly[1] this CSS variable won't be updated and consequently things won't work as intended. This is purposely implemented such that when a `PDFPageView`-instance is part of a viewer, we don't repeatedly set the CSS variable for every single page. --- [1] See e.g. the "pageviewer" example in the `examples/components/` folder.
|
/botio-linux preview |
From: Bot.io (Linux m4)ReceivedCommand cmd_preview from @timvandermeij received. Current queue size: 0 Live output at: http://54.67.70.0:8877/3a179d26daf1bf7/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.67.70.0:8877/3a179d26daf1bf7/output.txt Total script time: 5.46 mins Published |
timvandermeij
approved these changes
Aug 5, 2021
|
Looks good! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Without this patch, when using
PDFPageViewdirectly[1] this CSS variable won't be updated and consequently things won't work as intended.This is purposely implemented such that when a
PDFPageView-instance is part of a viewer, we don't repeatedly set the CSS variable for every single page.[1] See e.g. the "pageviewer" example in the
examples/components/folder.