Skip to content

Tolerate a drawable without a skin when fencing a position - #2

Merged
Mistium merged 1 commit into
developfrom
error-dump-fixes
Sep 24, 2026
Merged

Mistium merged 1 commit into
developfrom
error-dump-fixes

Conversation

@Mistium

@Mistium Mistium commented Sep 24, 2026

Copy link
Copy Markdown
Member

A target can move while its skin is still loading or after the skin was destroyed. getFencedPositionOfDrawable already tolerated a missing drawable but dereferenced drawable._skin unconditionally, so a go to block on such a target threw "Cannot read properties of undefined (reading 'getFenceBounds')" (seen with the Canvas extension). With no skin there is nothing to fence against, so the requested position is returned unchanged.

Unit test added; the tap unit and integration suites pass locally after a build. No visible change, so no screenshots.

A target can move while its skin is still loading or after the skin was destroyed. getFencedPositionOfDrawable already tolerated a missing drawable but dereferenced the skin unconditionally, so a "go to" block on such a target threw "Cannot read properties of undefined (reading 'getFenceBounds')". Keep the requested position when there is nothing to fence against.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@Mistium
Mistium merged commit 5aa15d7 into develop Sep 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant