Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
Fix WebAgg initialization#19131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This is already done in the WebSocket's `onopen` function, and sendingit during the object's initialization crashes due to the WebSocket notbeing ready.Fixesmatplotlib#19129.
Because this is behind the asynchronous `ResizeObserver`, it does _not_cause a failure to initialize the JavaScript figure, but is similar inerror as the previous commit.
attn@ianhi |
I tested locally and this works again. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
This fixes the issue for me as well.
I'm going to merge on the strength of@ianhi review and this being a critical fix. |
Not sure why this didn't backport? @meeseeksdev backport to v3.3.x |
…131-on-v3.3.xBackport PR#19131 on branch v3.3.x (Fix WebAgg initialization)
PR Summary
Sending the pixel ratio in initialization fails because the WebSocket is not open yet; this is already sent in the
onopen
handler, so just remove it from initialization.Also, fix a similar bug in sending resizes too early. This one is non-fatal because it is in an async handler.
PR Checklist
pytest
passes).flake8
on changed files to check).flake8-docstrings
and 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).