Revert 'Fabric-compatible implementation of feature' and have Fabric noop when setJSResponder is called for now (#21009)
Joshua Gross committed
Mar 15, 2021 at 12:22 UTC
f8979e0e28398d98dab921f17d14a5a9b5fb1b71
3 files changed
+1
-9
packages/react-native-renderer/src/ReactFabricGlobalResponderHandler.js
+1
-7
@@ -16,13 +16,7 @@ const ReactFabricGlobalResponderHandler = {
16
const isFabric = !!fromOrTo.stateNode.canonical._internalInstanceHandle;
17
18
if (isFabric) {
19
- if (from) {
20
- nativeFabricUIManager.setIsJSResponder(from.stateNode.node, false);
21
- }
22
-
23
- if (to) {
24
- nativeFabricUIManager.setIsJSResponder(to.stateNode.node, true);
25
- }
19
+ // Noop for now until setJSResponder/clearJSResponder are supported in Fabric
20
} else {
21
if (to !== null) {
22
const tag = to.stateNode.canonical._nativeTag;
packages/react-native-renderer/src/__mocks__/react-native/Libraries/ReactPrivate/InitializeNativeFabricUIManager.js
-1
@@ -176,7 +176,6 @@ const RCTFabricUIManager = {
176
);
177
success(1, 1, 100, 100);
178
}),
179
- setIsJSResponder: jest.fn(),
179
};
180
181
global.nativeFabricUIManager = RCTFabricUIManager;
scripts/flow/react-native-host-hooks.js
-1
@@ -179,7 +179,6 @@ declare var nativeFabricUIManager: {
179
locationY: number,
180
callback: (Fiber) => void,
181
) => void,
182
- setIsJSResponder: (node: Node, isJsResponder: boolean) => void,
182
...
183
};
184