From 53d37f72e5d8bc0f074697d27acdb61889fb0e05 Mon Sep 17 00:00:00 2001 From: Eric Rozell Date: Tue, 24 Sep 2024 14:55:42 -0700 Subject: [PATCH] Fix PointerOverOut test (#46634) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/46634 The PointerEventPointerOverOut.js test case is broken due to a changed assumption about the name of the native tag property (`_nativeTag` vs. `__nativeTag`). This fixes the broken assumption. ## Changelog [General][Fixed] Fixed issue with W3C PointerEvents tests Reviewed By: NickGerleman Differential Revision: D63336621 --- .../W3CPointerEventPlatformTests/PointerEventPointerOverOut.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/rn-tester/js/examples/Experimental/W3CPointerEventPlatformTests/PointerEventPointerOverOut.js b/packages/rn-tester/js/examples/Experimental/W3CPointerEventPlatformTests/PointerEventPointerOverOut.js index 5358381de5d1..6ffc64c010fc 100644 --- a/packages/rn-tester/js/examples/Experimental/W3CPointerEventPlatformTests/PointerEventPointerOverOut.js +++ b/packages/rn-tester/js/examples/Experimental/W3CPointerEventPlatformTests/PointerEventPointerOverOut.js @@ -26,7 +26,7 @@ function getNativeTagFromHostElement( } if (elem != null) { // $FlowExpectedError - accessing non-public property - return elem._nativeTag; + return elem.__nativeTag; } return undefined; }