native: simulate pressable event bubbling

[davidisaaclee]

To preface: I don't know if this is a great thing to add to the Pressable primitive – opening this for discussion. Alternatives include (1) plumbing a disabled prop to ChatMessage for my one use case, (2) adding a flag to Pressable to opt-in to this behavior, or (3) creating a new Pressable-like component with this behavior (OptionallyPressable? 🤷 ).

---

I was trying to add a long-press to a container view holding a ChatMessage using Pressable. My handler wouldn't get called – swapping out ChatMessage for a blank View worked.

ChatMessage has a Pressable which has no bound handlers in this scenario, and I expected events to bubble up the stack like on web – but it looks like RN doesn't have that behavior. Here's a recording of the fixture from this PR demonstrating this – the specific case is when Enable inner press handler is off and I'm tapping on the inner view – I expect that the inner view does not activate (because no handler) and the outer view's handler does activate (since I'm tapping over the outer view):

passthru-pressable-before.mov

To solve my initial problem:

1. If I could "reach across" to the ChatMessage's Pressable, setting pointerEvents="none" would work
2. Setting disabled on the inner Pressable passes events through to ancestors

(1) seems violent to do for every use case – I'd prefer a component that can be optionally interactive, and when the component is configured to be non-interactive, events naturally pass through to ancestors.

6847213 implements (2) – setting disabled={true} when there are no bound handlers.

passthru-pressable-after.mov

---

I think there's a solution here if we were to move to react-native-gesture-handler instead of the Tamagui pressable mixin, but I don't think it'd be very different in implementation – I think we'd still be disabling interaction when missing handlers. (There are APIs for composing gestures but they require references to the relevant gestures, which would be a lot of plumbing.)

[latter-bolden]

This was definitely a point of confusion for me when first working with RN. The approach you implemented feels sensible, I think it will be less surprising to have the clicks bubble by default. Curious if others have thoughts!

We should however make sure this doesn't behave strangely anywhere in existing code. Would prefer to avoid merging until after we cut this week's release.

[dnbrwstr]

Makes sense to me -- @patosullivan could you take a look? As you've spent time in pressable most recently.

[davidisaaclee]

wanted to add more context that I realized was missing:

• This is not really bubbling, since we can't receive the press event on both the outer and inner views (i.o.w. we can't optionally preventDefault) – this is more about treating an inert Pressable as any other non-interactive view
• I'd be open to any alternative solutions to my initial issue – I just couldn't think of any apart from the ones I posted in OP

[patosullivan]

Makes sense to me!

[davidisaaclee]

great – I'll merge this on Friday afternoon after the build review

[dnbrwstr]

Lgtm when you're ready to merge!