6 months ago
e2b7051The web/IAB shell was reusing the desktop topbar toolbar class, which sets containers to relative positioning. That overrode the inline absolute placement on the sidebar and context collapse controls, so the sidebar toggle was rendered as a normal flex item at the far right of the header instead of staying pinned to the left edge. Split the floating toolbar layer styling out so the browser-shell controls keep their explicit positioning while native platform variants still share the same z-index behavior. Constraint: The same AppTopBar component serves browser, Linux, macOS, and Windows layouts Rejected: Hardcode browser-only inline styles for the left toggle | fixes one control but leaves the shared floating toolbar contract inconsistent Confidence: high Scope-risk: narrow Reversibility: clean Directive: Do not mix shared positioning classes with utility-driven absolute toolbar placement in AppTopBar Tested: bun test apps/desktop/test/app-topbar.test.tsx apps/desktop/test/sidebar-ui.test.tsx; bun run typecheck:desktop; live Chrome verification via Computer Use in expanded and collapsed states; headless Chrome bounding-box verification at 1204x1084 Not-tested: full bun test
Parentbc0f39d
