import { CSSProperties, ReactNode, useRef } from 'react' import { useMatch } from 'react-router' import BottomNav from '../components/Layout/BottomNav' import ErrorBoundary from '../components/shared/ErrorBoundary' import MBottomNav from './components/MBottomNav' import MNavRail from './components/MNavRail' import { useSizeClass } from '../hooks/sizeClass' import MKeyboardHost from './keyboard/MKeyboardHost' import MShellShortcuts from './keyboard/MShellShortcuts' import MToastHost from './components/MToastHost' import MEdgeBack from './components/MEdgeBack' import { useNativeCapabilities } from '../native/capabilities' import { isNativeIos } from '../native/platform' import { useWindowFold } from '../native/windowFold' import './mobile.css' interface MobileShellProps { isPhone: boolean children: ReactNode } /** * Shell around every protected page. Below the md breakpoint it is the root * of the new mobile experience: scopes the --m-* design tokens, paints the * screen gradient, hosts the bottom dock, the sheet portal target and the * mobile toast presenter. From 768px up it renders the exact legacy wrapper * unchanged. Both branches share the div > div > children shape so pages keep * their state when the viewport crosses the breakpoint (rotation, * split-screen) instead of remounting. * * On the phone the shell deliberately owns no scroll container (#1809): the * document is the scroller, because that is the only movement iOS Safari * minimises its address bar for. Screens that want a full-viewport layout * (map screens, the trip planner) set their own height instead of borrowing * one from here. */ export default function MobileShell({ isPhone, children }: MobileShellProps) { // The trip planner (/trips/:id) is a full-screen takeover that ships its own // in-trip dock (MTripShell). The global dock must not render underneath it: // on iOS Safari a position:fixed nav paints THROUGH the trip overlay's higher // stacking context, so the wrong (global) bar shows on top of the trip screen. const inTripPlanner = useMatch('/trips/:id') // The app's own edge swipe back, where the binary has turned WebKit's off. const { caps } = useNativeCapabilities() const pageRef = useRef(null) const edgeBack = isNativeIos() && caps.features.includes('edgeBack') // On a wide window (an iPad, a foldable unfolded) the rail on the leading edge // replaces the dock, and the page column starts after it. The class goes on the // root as data-size: the wide:/split: variants and mobile.css key on it. const sizeClass = useSizeClass() const wide = sizeClass !== 'compact' // A foldable's fold, as the Android app reports it: two-pane screens end their // leading pane there (mobile.css, data-fold). const fold = useWindowFold() const foldStyle = fold ? ({ '--m-fold-start': `${fold.start}px`, '--m-fold-end': `${fold.end}px` } as CSSProperties) : undefined if (!isPhone) { return (
{children}
) } return ( // min-h-svh, not min-h-dvh: dvh grows while Safari's toolbar retracts, so a // dvh page length would chase the animation it just triggered.
{/* Background and screen gradient live on their own viewport-sized layer. The shell root is as tall as the document now, and --m-scr is a radial gradient measured against its element box, so on it the light cone would be stretched over the whole scroll length. It stays on a NEGATIVE z-index, and the content wrapper stays unpositioned on purpose. Lifting the layer into the positioned range means the content has to be positioned too, which makes it a stacking context and clamps every fixed overlay a screen renders inside it: the vacay view/edit FAB (z-50) ended up underneath the dock (z-40) that way. For the negative layer to be visible, body must not paint over it, which index.css handles for this breakpoint. */}
{/* The rail comes before the page in the document, as it does on screen, so a keyboard (Full Keyboard Access on an iPad) reaches the navigation first. It is fixed, so where it sits in the DOM moves nothing. */} {!inTripPlanner && wide && ( )}
{children}
{!inTripPlanner && !wide && ( )} {/* A hardware keyboard (an iPad's, mostly) gets the shortcuts an iPad app has. */}
) }