Fix ScaleManager not resizing to parent container (#7213) #7222
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.
This PR fixes issue #7213 where the ScaleManager fails to resize the game canvas
to match the size of its parent container.
Root Cause:
The window resize handler only updated canvas bounds, but did not re-measure the
parent container size. As a result, the Scale Manager used outdated parent size
values, causing the canvas to display incorrectly after window resize or mobile
orientation changes.
Fix:
Tested:
Result:
The canvas now consistently fills the parent container without clipping,
shifting, or leaving empty space.
This resolves #7213.
Note
On window resize, recalculate parent bounds and refresh scaling so the canvas correctly resizes to its parent.
src/scale/ScaleManager.js):getParentBounds()andrefresh()insidelisteners.windowResizeafterupdateBounds()to ensure canvas resizes to current parent size.Written by Cursor Bugbot for commit 108e196. This will update automatically on new commits. Configure here.