6 months ago
bc0f39dThe shared settings shell relied on platform CSS to absolutely position the drag-zone overlay. In the web browser that rule never applied, so the drag zone became the first grid child and pushed the nav and main pane into the broken stacked layout captured in review. This also tightens the responsive collapse threshold so review-width browser panes around 900px keep the intended left-nav/right-content structure. Constraint: The same settings shell is shared across Electron and browser rendering paths Rejected: Remove the drag zone entirely | desktop titlebar drag affordance still needs the overlay Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep non-content overlays out of grid and flex flow in shared shell components Tested: bun test apps/desktop/test/settings-shell.test.ts; bun run typecheck:desktop; live Chrome verification at full width via Computer Use; headless Chrome verification at 891px and 820px widths via puppeteer-core Not-tested: full bun test
Parent05727ac
