Skip to content
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

Options.overlay.interceptTouchOutside disfunctional #7797

Closed
1 task done
aight8 opened this issue Oct 14, 2023 · 3 comments
Closed
1 task done

Options.overlay.interceptTouchOutside disfunctional #7797

aight8 opened this issue Oct 14, 2023 · 3 comments

Comments

@aight8
Copy link

aight8 commented Oct 14, 2023

What happened?

When I display an overlay screen, and set the interceptTouchOutside option to false, it is not possible to interact with UI elements on the screen behind it.

What was the expected behaviour?

If I display an overlay screen (component layout), and set the interceptTouchOutside option to false (no matter if in the defaults, in showOverlay or on the screen component options), it should be possible to interact with elements on the screen behind (behind the overlay screen).

Was it tested on latest react-native-navigation?

  • I have tested this issue on the latest react-native-navigation release and it still reproduces.

Help us reproduce this issue!

Navigation.showOverlay({
	component: {
		name: 'OverlayComponent',
		options: {
			layout: {
				componentBackgroundColor: 'transparent',
			},
			overlay: {
				interceptTouchOutside: false,
			}
		},
	},
})

In what environment did this happen?

React Native Navigation version: 7.37.1
React Native version: 0.72.6
Has Fabric (React Native's new rendering system) enabled: no
Node version: 20.8.0
Device model: iPhone 13 Pro (device)
iOS version: 17.1

@aight8
Copy link
Author

aight8 commented Oct 16, 2023

It's an issue with react-native-gesture-handler
software-mansion/react-native-gesture-handler#514

@aight8 aight8 closed this as completed Oct 16, 2023
@james-ovens-eurostar
Copy link

This is still a problem, I don't think this issue should be closed just because the problem originates in another library being used

@donatoaguirre24
Copy link

donatoaguirre24 commented Dec 10, 2024

@james-ovens-eurostar in case it helps, we were able to workaround the issue by setting pointerEvents="box-none" in the root view. So the overlay container doesn't steal the touch events (the overlay content will still respond to them)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants