-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Expose onHoverIn/onHoverOut on Pressable #8972
Comments
Similar macOS issue: microsoft/react-native-macos#871 |
This is going to be pulled in as part of the next RN integration we do. We are currently at Oct 21st, and the change in question was merged on Oct 23rd. @NickGerleman is probably going to pull this in within a week or so. |
@rectified95 you and @chiaramooney are on rotation for November 🙂. |
That is very true :D |
If I read the updates to this bug properly, the upstream change will be merged in ~ next week, and will land with RN 0.68? |
Very unlikely, FB generally doesn't backport features to older versions. |
Sorry, I meant RN-Windows 0.64, not RN Core |
Summary
With facebook/react-native#32405 , The Stock Pressable component now exposes onHoverIn/onHoverOut as the way to support mouse events. We should align our desktop ports (rn-macos/windows/win32) to take advantage of this.
Motivation
This issue is motivated by my want to use the RN Stock Pressable component in FluentUI React Native, which currently has a local copy of Pressable internally. Using the upstream component would mean less custom code and smaller bundle size for FluentUI React Native. It also will help push Pressable as "the" cross platform component for handling mouse / keyboard focus / press events.
Basic Example
No response
Open Questions
No response
The text was updated successfully, but these errors were encountered: