-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Pressables not working after context menu opened #24
Comments
Whoa I'll have to check this out for sure. Thanks for the bug report! |
i have same problem, did u solved this? |
Still happens sometimes |
try to use rn ios context menu view its much better |
I think this is because the native UIControl hijacks the press event no matter what on iOS. Not sure tho |
Still happens. Also here is error message that follows this behavior (if you are trying to navigate somewhere after screen freezing)
|
When wrapping Pressables (
<Pressable>
,<TouchableOpacity>
, ...) with a context menu, the entire JS responder system will fail/crash once you open the context menu once. In other words, your entire screen becomes unresponsive if you open a context menu that contains a pressable.There might be some extra treatment required to support inlining the JS pressability API.
(Also, it looks like native buttons such as the back button from react-native-navigation are still working, it's just the current screen that "freezes"/doesn't trigger onPress events anymore)
Screen.Recording.2021-01-18.at.10.49.40.mov
Code:
The text was updated successfully, but these errors were encountered: