-
-
Notifications
You must be signed in to change notification settings - Fork 839
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
avm2: Access Event.target in dispatchEvent #19236
avm2: Access Event.target in dispatchEvent #19236
Conversation
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.
To be sure, this means the clone logic will never trigger if we (as in, native code) are the ones doing dispatching. I'm assuming we're considering it safe?
Can you please also copy the test from my PR? It test a more real-world case and a getter being hit.
I tested it- none of the "automatically" dispatched events (
I was going to ask you :P |
… clone when dispatching event
1c23364
to
e4d5f7e
Compare
Rebase failed
e4d5f7e
to
fc217ab
Compare
GitHub had a brainfart and thought that a no-op rebase would fail, so I force-pushed the last commit with the same changes, hopefully it will work this time. |
Rebase failed
Narrator: It did not. |
…ine whether to call clone Test written by Adrian17
fc217ab
to
765576b
Compare
Third time's the charm! 🎉 |
Like #19127, but clones the Event in
EventDispatcher.dispatchEvent
instead ofevents::dispatch_event
.