Replies: 3 comments 4 replies
|
just saw this related answer as well: #276 (comment) |
0 replies
|
FYI: I am encountering this bug: gorhom/react-native-bottom-sheet#2201 also reported here: software-mansion/react-native-gesture-handler#3445 Considering that storybook is quite commonly used, was wondering if maybe somebody observed similar issues and/or is able to reproduce on a some other codebases? As mentioned in the discussion not sure if the issue is on storybook, bottom-sheet, or the gesture handler. But the gut feeling is that there might be some kind of conflict between gesture handler and how pointer events work with the flag enabled? But might be a very wild guess... |
3 replies
|
Please report the bug to the React Native github page |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The documentation is not clear about the requirement for the PointerEvents feature flag to be enabled in react native (https://reactnative.dev/blog/2022/12/13/pointer-events-in-react-native#enable-feature-flags)
Is it safe to assume this is indeed a hard requirement? Otherwise the type of
htmlcomponents would not be valid with events that are ignored and needed alternatives missing (e.g onHoverIn, onHoverOut, etc.).beside the possibility of improving the documentation on that, I have some related doubts:
onPointer*events, or it also affect something else (e.g.onClick?)All reactions