{{ message }}
nbagg: Store DPI ratio on figure instead of window. - #18361
Merged
Merged
Conversation
This prevents existing figures from breaking if a followup figure fails to initialize its canvas and overwrites the (global) window ratio. See matplotlib#17576 (comment).
timhoffm
approved these changes
Aug 27, 2020
Member
tacaswell
added a commit
to tacaswell/matplotlib
that referenced
this pull request
Sep 14, 2020
FIX: Store DPI ratio on figure instead of window for nbagg/webagg
Merged
This file contains hidden or 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
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.

PR Summary
This prevents existing figures from breaking if a followup figure fails to initialize its canvas and overwrites the (global) window ratio.
See #17576 (comment).
PR Checklist
pytestpasses).flake8on changed files to check).flake8-docstringsandpydocstyle<4and runflake8 --docstring-convention=all).doc/users/next_whats_new/(follow instructions in README.rst there).doc/api/next_api_changes/(follow instructions in README.rst there).