@granite-js/micro-frontend 2.5.3 → 2.5.5

package/CHANGELOG.md

@@ -1,5 +1,36 @@
 # @granite-js/micro-frontend
 
+## 2.5.5
+
+### Patch Changes
+
+- @granite-js/utils@2.5.5
+
+## 2.5.4
+
+### Patch Changes
+
+- 271ef06: Put a detached portal source in the same measurement space React Native uses on Android.
+
+  A controller surface that is not attached to a window cannot read its own position, so the portal
+  offset was taken from the host origin and came out as zero. Fabric applies that offset as the
+  portal's transform, and that transform is what `measureInWindow` reports — the rendered position
+  comes from the host and never depended on it. The result was that a teleported subtree reported raw
+  screen coordinates while an ordinary window-attached surface reported coordinates relative to the
+  window's visible content area, the two disagreeing by the system bars inset. Anything consuming those
+  coordinates natively — an app bridge that draws at a measured rect, for one — landed a status bar
+  height off.
+
+  The detached branch now asks `RootViewUtil.getViewportOffset` about the host instead of deriving the
+  offset itself. That is the same call React Native makes to place a surface root, so the two stay in
+  one space without this package restating the rule. It also keeps them together as that function
+  changes: through 0.85 it subtracts the visible display frame, while 0.86 subtracts `WindowInsetsCompat`
+  status bar and cutout insets and skips the subtraction entirely under edge-to-edge.
+
+  Rendering and touch are unaffected. The teleported children are parented by the host, so they draw
+  where the host puts them, and the touch path that dispatches to them does not follow this offset.
+  - @granite-js/utils@2.5.4
+
 ## 2.5.3
 
 ### Patch Changes

package/android/src/main/java/com/teleport/portal/PortalLayoutStateController.kt

@@ -1,7 +1,9 @@
 package com.teleport.portal
 
+import android.graphics.Point
 import android.view.View
 import com.facebook.react.bridge.Arguments
+import com.facebook.react.uimanager.RootViewUtil
 import com.facebook.react.uimanager.StateWrapper
 import com.teleport.extensions.dp
 import com.teleport.extensions.isDetached
@@ -61,22 +63,32 @@ internal class PortalLayoutStateController(
   }
 
   private fun createLayoutState(host: PortalHostView): PortalLayoutState {
-    val hostLocation = host.screenLocation()
-    // A detached controller surface has no Window coordinate space. Its children
-    // are already physically parented by the destination host, so use the host
-    // origin as the logical source origin and avoid applying a screen inset twice.
-    val sourceLocation =
+    // This offset is what `PortalViewShadowNode.getTransform` translates by, and that transform is
+    // what `measureInWindow` reports. Neither what these nodes render nor what they receive touches
+    // on depends on it: the children are physically parented by the host, and `TouchTargetHelper`
+    // walks the real View tree. So it decides only where they say they are.
+    //
+    // A detached controller surface cannot measure itself: `getLocationOnScreen` returns (0, 0) for
+    // a view with no window, so an offset derived from it lands the teleported subtree in a
+    // different space than an ordinary, window-attached surface. React Native puts a surface root
+    // into that space with `RootViewUtil.getViewportOffset`; asking it about the host, which is the
+    // view these children are actually parented by, puts them there too. Delegating rather than
+    // repeating the arithmetic also means the two stay together when React Native changes what
+    // `getViewportOffset` does — 0.86 rewrote it around `WindowInsetsCompat`, for one.
+    val offset =
       if (sourceView.isDetached()) {
-        hostLocation
+        RootViewUtil.getViewportOffset(host)
       } else {
-        sourceView.screenLocation()
+        val hostLocation = host.screenLocation()
+        val sourceLocation = sourceView.screenLocation()
+        Point(hostLocation[0] - sourceLocation[0], hostLocation[1] - sourceLocation[1])
       }
 
     return PortalLayoutState(
       hostWidth = host.width.toFloat().dp,
       hostHeight = host.height.toFloat().dp,
-      offsetX = (hostLocation[0] - sourceLocation[0]).toFloat().dp,
-      offsetY = (hostLocation[1] - sourceLocation[1]).toFloat().dp,
+      offsetX = offset.x.toFloat().dp,
+      offsetY = offset.y.toFloat().dp,
     )
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@granite-js/micro-frontend",
-  "version": "2.5.3",
+  "version": "2.5.5",
   "description": "Micro-frontend build, runtime, session, and Portal contracts for Granite brownfield applications",
   "main": "./dist/module/index.js",
   "types": "./dist/typescript/index.d.ts",
@@ -56,7 +56,7 @@
   },
   "dependencies": {
     "@babel/core": "7.28.5",
-    "@granite-js/utils": "2.5.3",
+    "@granite-js/utils": "2.5.5",
     "@standard-schema/spec": "^1.0.0"
   },
   "peerDependencies": {
@@ -72,8 +72,8 @@
   },
   "devDependencies": {
     "@babel/types": "7.28.5",
-    "@granite-js/plugin-core": "2.5.3",
-    "@granite-js/react-native": "2.5.3",
+    "@granite-js/plugin-core": "2.5.5",
+    "@granite-js/react-native": "2.5.5",
     "@types/babel__core": "^7.20.5",
     "@types/node": "24.10.12",
     "@types/react": "19.2.0",