- Shipped
- September 10, 2026 at 5:05 PM UTC
- Author
- Kamo
- Commit
- 2c933ec
Two follow-ups to 0c5ef994 (maximize beside the nav). A PINNED Interaction Center now takes its width away from the maximized pane. Pinned, the panel is worked alongside the screen, so a maximized window and its tab strip stop at the panel's left edge instead of running on underneath it. The panel publishes its width on a CSS variable while pinned AND open (useInteractionCenterReserve) and paneGeometry subtracts it, the way the rail's variable already works; the panel is drawn at the same string, so the two cannot disagree. Unpinned, the panel is still a modal over a scrim and the window keeps its width behind it. Unpinning, closing and unmounting all withdraw the reserve. The navigator's width cap measures the room to the panel's edge as well. Menus no longer open behind tool windows. The store's z counter (tool-core, shared with mobile) climbs on every open, raise and focus and is never reset; painted raw, a long session carried windows past MUI's 1300, and every menu, popover and dialog in the app then opened BEHIND them — in the DOM, positioned, invisible. The dock now reads the counter for ORDER only and paints each window at its rank in a small band above 200 (windowStacking.ts), so the stacking the store decided is kept and no window ever reaches a menu's layer. The nav's lift over a maximized pane uses the same painted level, so it stays under the menus too. Verified in real Chrome: the window and strip end at the pinned panel's edge (890px of 1440), an unpinned panel overlays without reflowing, and after 2,000 focus clicks (the counter past 1300) a menu at MUI's default layer still paints over the window.