You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The _onResize method in activity.js is being called before this.stage is properly initialized, which could lead to potential errors during the application startup. This occurs during the initial loading phase of Music Blocks.
Expected Behavior
The _onResize method should only execute its resize operations after this.stage has been properly initialized. Currently, we've added a defensive check, but the root cause of the early resize call should be investigated.
Screenshots
How to Reproduce
Load Music Blocks in browser
Open browser developer tools
Observe that _onResize is called during initialization
Check the timing of this.stage initialization versus the first resize call
Environment:
Operating System: All (This is a core initialization issue)
Browser: All modern browsers
Version of Software/Project: Current main branch
Checklist
I have read and followed the project's code of conduct.
I have searched for similar issues before creating this one.
I have provided all the necessary information to understand and reproduce the issue.
I am willing to contribute to the resolution of this issue.
The text was updated successfully, but these errors were encountered:
Description
The
_onResize
method inactivity.js
is being called beforethis.stage
is properly initialized, which could lead to potential errors during the application startup. This occurs during the initial loading phase of Music Blocks.Expected Behavior
The
_onResize
method should only execute its resize operations afterthis.stage
has been properly initialized. Currently, we've added a defensive check, but the root cause of the early resize call should be investigated.Screenshots
How to Reproduce
_onResize
is called during initializationthis.stage
initialization versus the first resize callEnvironment:
Checklist
The text was updated successfully, but these errors were encountered: