-
Notifications
You must be signed in to change notification settings - Fork 46.8k
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
Experimental event API: loosen EventTarget constraints and warnings #15292
Experimental event API: loosen EventTarget constraints and warnings #15292
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.
Relaxing the warning makes sense but for this to make sense we need to also change the semantics of it so that it picks up the parent element instead of nested child element in getElementFromTouchHitTarget.
export default function getElementFromTouchHitTarget( |
.return
path.
Apply fiber tree traversal Apply fiber tree traversal (remove null check) Apply fiber tree traversal (remove null check)
56e385b
to
57a1743
Compare
ReactDOM: size: -0.0%, gzip: -0.0% Details of bundled changes.Comparing: 4482fdd...57a1743 react-dom
react-art
react-native-renderer
react-test-renderer
react-noop-renderer
react-reconciler
Generated by 🚫 dangerJS |
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.
it seems right to me, thanks for the tests. I assume there's a plan to flesh the TODOs out in upcoming PRs.
…#15292) * Remove warning for event targets being direct children of event component * Addressed feedback and added more test coverage + warnings
Upon further internal discussion with @sebmarkbage in regards to the internal event API, this changes the
EventTarget
to not have the constraint on having to be a direct child of anEventComponet
, so they can be composed as so: