Do not fire anywidget change listeners at mount#10179
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The `WidgetBinding` replayed current model state at every `change:` listener a render had registered, once the render settled. A listener could therefore fire for a trait that did not change, and the widget would run those side effects at every mount (#10173). The replay is not necessary because model state is already current when render runs and deviates from anwidgets Jupyter.
Contributor
There was a problem hiding this comment.
Review completed against the latest diff
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
mscolnick
approved these changes
Jul 14, 2026
Contributor
|
🚀 Development release published. You may be able to view the changes at https://marimo.app?v=0.23.15-dev11 |
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.
Follow up to #10178
The
WidgetBindingreplayed current model state at everychange:listener a render had registered, once the render settled. A listener could therefore fire for a trait that did not change, and the widget would run those side effects at every mount (#10173).The replay is not necessary because model state is already current when render runs and deviates from anwidgets Jupyter.