Skip to content

Commit 0c5f81b

Browse files
fix(mobile): full-screen MCP apps are told only the safe area they occupy
Review finding (spec round 6, Fable 5.1): the full-screen modal already pads for the status bar and home indicator, so reporting those insets made apps pad twice. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
1 parent 4ec157f commit 0c5f81b

1 file changed

Lines changed: 3 additions & 6 deletions

File tree

‎apps/mobile/src/features/threads/McpAppWebView.tsx‎

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -297,13 +297,10 @@ export function ThreadMcpApp(props: {
297297
timeZone: Intl.DateTimeFormat().resolvedOptions().timeZone,
298298
userAgent: `t3-code/${Constants.expoConfig?.version ?? "0.0.0"}`,
299299
deviceCapabilities: { touch: true, hover: false },
300+
// The full-screen modal keeps the top and bottom insets for its
301+
// header and the home indicator; only the sides reach the app.
300302
safeAreaInsets: isFullscreen
301-
? {
302-
top: current.insets.top,
303-
right: current.insets.right,
304-
bottom: current.insets.bottom,
305-
left: current.insets.left,
306-
}
303+
? { top: 0, right: current.insets.right, bottom: 0, left: current.insets.left }
307304
: { top: 0, right: 0, bottom: 0, left: 0 },
308305
...(current.toolDefinition === undefined
309306
? {}

0 commit comments

Comments
 (0)