[Medformatik]

What changed and why

In the installed app the floating chrome sat further below the status bar than it needs to. Each element added the page's own edge spacing on top of the inset: the search bar sat 12px below the status bar, and the turn-by-turn banner 16px. On the same Pixel, Google Maps leaves 8px above its search bar; the status bar already separates the chrome from the edge of the screen.

topInset(edge, below) in lib/layout.ts now gives max(edge, inset + 8px). Under a status bar the chrome sits 8px below it; in a browser tab, where the inset is 0, the existing 12px or 16px stays. Every floating element at the top takes its offset from it:

• the search bar, the space reserved below it (sidebar, full-screen search results, street-level card and close button) and the category chip row;
• the search-in-area chip, the weather widget and the desktop account avatar;
• the driving and transit navigation banners, the search-along-route picker and the detail card shown beside them.

Full-screen dialogs, drawers, the settings and admin bars, and the bottom sheet's height cap are unchanged. Their content already starts directly below the status bar, as Google Maps' full-screen pages do.

Measured on the phone (density 2.44, status bar 161px): Google Maps' search pill starts at 180px. OpenMapX's started at 193px and now starts at 183px; the remaining 3px is the shadow. The driving banner moved from 202px to 183px, level with the search bar.

Verification

• Web vitest for lib/layout, components/navigation, search, map, panels and weather: 2,358 passed, including new tests for topInset and the search-bar clearance. tsc for apps/web, biome.
• On a Pixel (Android 17), the installed dev app loading this branch's web build: the search bar and chips (pictured), and the driving navigation banner, which I left out of the screenshot because it shows the phone's location.
• Not checked on the device: the street-level viewer (its coverage tiles do not load from the local setup), transit navigation, and iOS. Their offsets come from the same helper.

Release and upgrade impact

Product impact: ordinary