khldonAlkateeh
khldonAlkateeh
hey @MatiPl01 thanks for your time and the detailed explanation Do you think there’s any workaround for this in the meantime? I’m kind of stuck because of it and can’t...
@MatiPl01 Just to clarify. in my app I’m not using a Switch. I only used it in the example to make the issue easier to show. In fact, the element...
@Ghalia-saleh Unfortunately not yet..no solution. still struggling with this bug @MatiPl01 any update ?
@tjzel @patrycjakalinska @m-bert guys, can you help solve this bug?
@MatiPl01 hey I tried to patch the issue locally Here’s what I did: I changed it manually and `npx expo run:android ` Unfortunately, nothing changed. the touch issue still happens...
@MatiPl01 i tested it the issue still happens the issue isn’t caused by collapsable=true or nativeID.
@MatiPl01 Thank YOU Honestly, I felt relieved when I realized the issue isn’t caused by the collapsable or nativeID props. the root cause might be something else that’s actually fixable....
really appreciate your time @MatiPl01 first of all: great. now i have two issues 🤣 You're totally right regarding root cause, but it seems like in my case there was...
@MatiPl01 After digging deeper into react native source code, here is what i found: android strictly clips touch events based on the parent bounds. `isTouchPointInView` returns `false ` as soon...
Hey @MatiPl01 `it should also happen with React Native views under certain conditions, even without using Reanimated.` That’s a very good point i think(i'm not sure) the reason is that...