-
Notifications
You must be signed in to change notification settings - Fork 46.3k
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
Bug: onPointerEnterCapture and onPointerLeaveCapture result in unknown event handler property
#17883
Comments
There is support for pointer-events in v16.4.0: |
@KevinKelbie thanks but that blog post does not list |
@necolas what can I do to help this get fixed? This has been blocking me since Jan 21st. I'm using React 16.13.0 |
@tommedema are you sure this event exist? Can you send a link to ECMA specification? |
It's the same as the mouse event equivalents, they don't bubble and don't have a capture phase: https://reactjs.org/docs/events.html#mouse-events. You should use |
You're wrong. While |
Then React should fix its TypeScript typings to special case those events to not generate |
@rjgotten We removed these types in the types for 18. We reverted the backport to types for 17 and 16 since it caused too much breakage across the ecosystem due to TypeScript wrongfully inlining types during declaration emit. |
I am using |
Latest is 18.2.70 |
This was a very recent change, then? As in literally as it was brought up in this GH issue's discussion? Thanks for straightening out the confusion there. |
FTR DefinitelyTyped/DefinitelyTyped#68984 [@types/react] fix: remove onPointerEnterCapture & onPointerLeaveCapture |
React version: v16.12.0 from https://unpkg.com/react/umd/react.development.js
Steps To Reproduce
unknown event handler property
error in consoleLink to code example: https://jsfiddle.net/tommedema/1uqoemxs/2/
The current behavior
It displays a
unknown event handler property
warningThe expected behavior
The capturing phase of the onPointerEnter and onPointerLeave events should be supported
The text was updated successfully, but these errors were encountered: