test: use real mouse events in context-menu tooltip tests#11660
Merged
Conversation
Replace synthetic event helpers with sendMouseToElement / sendMouse so the integration test exercises the real contextmenu open path and the real listbox mouseleave path instead of bypassing them. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
web-padawan
approved these changes
May 6, 2026
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
2 participants
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.
Simplify the context-menu tooltip integration test and bring it closer to real user interaction. The test relied on synthetic helpers —
openMenu(target)(firesmouseover) andfire(_listBox, 'mouseleave')— plus extra plumbing around destructuring andrequestContentUpdate()that did not reflect actual usage.Changes
sendMouseToElement({ type: 'click', element: target })withopenOn = 'click', matching a real click.fire(_listBox, 'mouseleave')withsendMouse({ type: 'move', position: [0, 0] })so the browser dispatches a realmouseleave.sendMouseToElementmove on the parent item instead ofopenMenu(parent).requestContentUpdate()+nextRender()— overlay is closed, items render on open.getMenuItems(...)destructuring.🤖 Generated with Claude Code