fix: guard Node.contains() against non-Node event targets (#101)#103
Merged
Conversation
Co-authored-by: Ona <no-reply@ona.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Collaborator
Author
|
✅ UI verification passed — design spec compliance confirmed. All changes in this PR are runtime type-safety guards ( |
Collaborator
Author
|
✅ Post-merge verification passed. E2E suite: 27/27 tests passed against Ad-hoc smoke tests — routes tested:
Skipped: No console errors detected (unauthenticated or authenticated). |
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
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.
Closes #101
What
TypeError: Failed to execute 'contains' on 'Node': parameter 1 is not of type 'Node'was thrown in editor event handlers whenMouseEvent.relatedTargetorEvent.targetwas a non-NodeEventTarget(e.g. when the mouse leaves to a cross-origin iframe or the browser window). The code used unsafeas Node/as HTMLElementcasts on these properties before passing them toNode.contains()andElement.closest().How
Replaced all unsafe
ascasts onevent.targetandevent.relatedTargetwithinstanceof Node/instanceof HTMLElementguards in three locations:draggable-block-plugin.tsx—handleMouseMove,handleMouseLeave, andhandleMenuMouseLeavepage-search.tsx—handleClickOutsideAdded a DOM event target safety convention to
.agents/conventions.mdto prevent this class of bug from recurring.Testing
Added
node-contains-safety.test.ts— a static analysis test that scans all component source files for unsafeas Nodeoras HTMLElementcasts onevent.target/event.relatedTarget. The test fails if any such pattern is found, ensuring future code follows theinstanceofguard convention.Full CI passes:
pnpm lint && pnpm typecheck && pnpm test(58 tests) andpnpm test:e2e(27 tests).