Fix measureInWindow on Android edge-to-edge

[zoontek]

Summary:

Fixes measureInWindow on Android when edge-to-edge is enabled.

Both ReactSurfaceView.viewportOffset and RootViewUtil.getViewportOffset subtract the visible window frame (status bar insets, split screen offsets) from getLocationOnScreen / getLocationInWindow coordinates. This is incorrect in edge-to-edge mode, where the content already extends behind system bars.

Related issue: #50509

Changelog:

[ANDROID] [FIXED] - Fix measureInWindow returning incorrect coordinates when edge-to-edge is enabled

Test Plan:

Tested measureInWindow with and without edge-to-edge enabled, in both single-window and split-screen configurations. Verified that returned coordinates correctly reflect the view's position relative to the visible content area.

For that, in RNTesterActivity.kt, comment:

// reactDelegate?.reactRootView?.let { rootView ->
//   val insetsType: Int =
//       WindowInsetsCompat.Type.systemBars() or WindowInsetsCompat.Type.displayCutout()

//   val windowInsetsListener = { view: View, windowInsets: WindowInsetsCompat ->
//     val insets = windowInsets.getInsets(insetsType)

//     (view.layoutParams as FrameLayout.LayoutParams).apply {
//       setMargins(insets.left, insets.top, insets.right, insets.bottom)
//     }

//     WindowInsetsCompat.CONSUMED
//   }
//   ViewCompat.setOnApplyWindowInsetsListener(rootView, windowInsetsListener)
// }

And in RNTesterAppShared.js replace export default RNTesterApp with:

export default () => {
  const ref = React.useRef<View>(null);
  const [measure, setMeasure] = React.useState<string>('');
  const [measureInWindow, setMeasureInWindow] = React.useState<string>('');
  const [onLayoutOutput, setOnLayoutOutput] = React.useState<string>('');
  React.useLayoutEffect(() => {
    ref.current?.measure(
      (
        x: number,
        y: number,
        width: number,
        height: number,
        pageX: number,
        pageY: number,
      ) => {
        setMeasure(
          `(${x}, ${y}) / ${width} x ${height}; \n  page=(${pageX}, ${pageY})`,
        );
      },
    );
  }, []);
  React.useLayoutEffect(() => {
    ref.current?.measureInWindow(
      (x: number, y: number, width: number, height: number) => {
        setMeasureInWindow(`(${x}, ${y}) / ${width} x ${height};})`);
      },
    );
  }, []);
  return (
    <View
      ref={ref}
      style={{flex: 1, justifyContent: 'center'}}
      onLayout={e => {
        setOnLayoutOutput(JSON.stringify(e.nativeEvent.layout));
      }}>
      <Text>Measure: {measure}</Text>
      <Text>measureInWindow: {measureInWindow}</Text>
      <Text>onLayout: {onLayoutOutput}</Text>
    </View>
  );
};

Screenshots:

Android 16 / edge-to-edge on - current behavior

Android 16 / edge-to-edge on - with fix

Android 14 / edge-to-edge off - current behavior

Android 14 / edge-to-edge off - with fix (no change)

[meta-codesync]

@alanleedev has imported this pull request. If you are a Meta employee, you can view this in D101308387.

[zoontek]

The logic is similar to RootViewUtil.getViewportOffset(v: View), it's just not used here because of it's bad naming (getViewportOffset could be called for any view, not just the root one)

[alanleedev]

copying here comment from @javache

I don't think react.runtime can depend on react.views? There seems to be a dependency issue.
Maybe the feature flag should live in UIManager/

[zoontek]

we could move isEdgeToEdgeFeatureFlagOn / setEdgeToEdgeFeatureFlagOn / updateEdgeToEdgeFeatureFlag in a separate file, but that introduces a change in the public API

[alanleedev]

FYI, com.facebook.react.views.view.isEdgeToEdgeFeatureFlagOn was add in June 2025.
@javache I also don't see any build issues so is this more of an architectural policy?

[react-native-bot]

This pull request was successfully merged by @zoontek in 9d18367

^{When will my fix make it into a release? | How to file a pick request?}