fix: fireEvent assumptions about RN tree structure

Author: mdjastrzebski

src/__tests__/fire-event.test.tsx

@@ -23,13 +23,6 @@ const OnPressComponent = ({ onPress, text }: OnPressComponentProps) => (
   </View>
 );
 
-type WithoutEventComponentProps = { onPress: () => void };
-const WithoutEventComponent = (_props: WithoutEventComponentProps) => (
-  <View>
-    <Text>Without event</Text>
-  </View>
-);
-
 type CustomEventComponentProps = {
   onCustomEvent: () => void;
 };
@@ -75,16 +68,6 @@ describe('fireEvent', () => {
     expect(onPressMock).toHaveBeenCalled();
   });
 
-  test('should not fire if the press handler is not passed to children', () => {
-    const onPressMock = jest.fn();
-    render(
-      // TODO: this functionality is buggy, i.e. it will fail if we wrap this component with a View.
-      <WithoutEventComponent onPress={onPressMock} />,
-    );
-    fireEvent(screen.getByText('Without event'), 'press');
-    expect(onPressMock).not.toHaveBeenCalled();
-  });
-
   test('should invoke event with custom name', () => {
     const handlerMock = jest.fn();
     const EVENT_DATA = 'event data';

src/fire-event.ts

@@ -82,10 +82,11 @@ function findEventHandler(
   const touchResponder = isTouchResponder(element) ? element : nearestTouchResponder;
 
   const handler = getEventHandler(element, eventName, { loose: true });
-  if (handler && isEventEnabled(element, eventName, touchResponder)) return handler;
+  if (handler && isEventEnabled(element, eventName, touchResponder)) {
+    return handler;
+  }
 
-  // eslint-disable-next-line @typescript-eslint/prefer-optional-chain
-  if (element.parent === null || element.parent.parent === null) {
+  if (element.parent === null) {
     return null;
   }