refactor: make touch target resolution policy explicit#510
Merged
Conversation
thymikee
force-pushed
the
codex/touch-target-resolution-policy
branch
from
d232598 to
11709bb
Compare
|
thymikee
force-pushed
the
codex/touch-target-resolution-policy
branch
from
11709bb to
74c3e6e
Compare
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.
Summary
Make touch coordinate resolution return explicit policy reasons while preserving the existing node-returning API.
Add focused tests for semantic tab buttons, hittable row promotion, same-rect descendant promotion, and broad ancestor avoidance.
Closes #509.
Touched files: 2. Scope stayed within the interaction resolver/tests.
Validation
pnpm formatpnpm exec vitest run src/__tests__/runtime-interactions.test.tspnpm check:quick