fix(staged): adapt traffic-light spacer - #853
Conversation
Signed-off-by: Matt Toohey <contact@matttoohey.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 446f0fe655
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| } | ||
|
|
||
| export function getTrafficLightSpacerWidth(isMobile: boolean): number { | ||
| if (!isTauri || !windowChrome.isMac || isMobile || windowChrome.isFullscreen) return 0; |
There was a problem hiding this comment.
When the macOS Tauri window is resized below the mobile breakpoint, viewport.isMobile becomes true even though the native traffic-light controls are still visible (the Tauri config allows desktop widths down to 375px with titleBarStyle: "Overlay"). This condition then collapses the spacer to 0, letting the Back button or other left actions sit underneath the traffic lights; the previous CSS still reserved 58px at this breakpoint. Only actual non-windowed/mobile contexts should remove the spacer.
Useful? React with 👍 / 👎.
1 participant
Summary
Testing