-
Notifications
You must be signed in to change notification settings - Fork 366
Remove accidental onMouseDown handler #5405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🎭 Playwright Test Results✅ All tests passed across all browsers! ⏰ Completed at: 09/07/2025, 02:55:34 AM UTC 📊 Test Reports by Browser🎉 Your tests are passing across all browsers! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's hope this is adequately covered by the tests 🤞🏻
It's a travesty that there's now green lines in the PR, but I've added a test that is harder to overwrite than the snapshots. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great catch
@AustinMroz Backport to Please manually cherry-pick commit Conflicting files
|
* Remove accidental onMouseDown handler * Fix test snapshot * Add test that onMouseDown isn't overwritten
#5079 removed the onMouseDown handler because it would overwrite prototype onMouseDown handlers added by custom nodes. This handler was accidentally re-added by #4263.
As the replacement mouse handling code added by #5079 still exists, only the removal of the onMouseDown code is required here.
EDIT: Looks like it also reverted test changes.
┆Issue is synchronized with this Notion page by Unito