Michał Osadnik 69a23f1c9f Remove blocking touch interactions if more than one active scree… (#296) ...

We believe that it might be better to manage the logic of blocking interactions from JS with setNativeProps and pointerEvents.

The current logic leads to some issues we're facing within React Navigation. There might be a state when more that one screen can be active. E.g. in modals we want to have two screens visible on the stack and have enabled interaction on the bottom one.

New code should not give any issues, because even though we need to handle activation of each screen from JS and this will just introduce an additional native call for enabling / disabling pointer events.

On iOS, we're not using React Native Screens in React Navigation for now and we'd like to focus on it later because right now we're not observing that crucial performance issues.

2020-01-27 11:07:07 +01:00

..

com/swmansion/rnscreens

Remove blocking touch interactions if more than one active scree… (#296)

2020-01-27 11:07:07 +01:00