fix: guard null viewport position in content bounds - #181
Open
dazzatronus wants to merge 1 commit into
Open
Conversation
Toolbar positioning reads viewportContainer.position via optional chaining that stopped at the container. When position is still null before the viewport is ready, accessing .x/.y threw. Chain through position so updates no-op safely until the viewport is initialized.
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
1 participant
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.
Why
getContentBoundsusedviewportContainer?.position.x, which still throws whenpositionis null. Toolbar rAF updates hit this before the viewport is ready.Verify
npx jest tests/content-bounds.test.tsposition.xduring early frames / before viewport ready.Risk
Low. Bounds fall back to origin (0) until position exists; same as missing container.