From e8936b8969e78e07d9a8bf2b6a22ce59a38f5dfb Mon Sep 17 00:00:00 2001
From: Lukas <134181853+bo2themax@users.noreply.github.com>
Date: Thu, 3 Sep 2026 09:16:32 +0200
Subject: [PATCH] macOS: follow up cascading fix for #14118
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Didn't respect the comment above before when reverting and testing hidden title 🫪
---
 macos/Sources/Features/Terminal/TerminalController.swift | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/macos/Sources/Features/Terminal/TerminalController.swift b/macos/Sources/Features/Terminal/TerminalController.swift
index 40089be15..7070a4867 100644
--- a/macos/Sources/Features/Terminal/TerminalController.swift
+++ b/macos/Sources/Features/Terminal/TerminalController.swift
@@ -297,9 +297,11 @@ class TerminalController: BaseTerminalController, TabGroupCloseCoordinator.Contr
                 if !window.styleMask.contains(.fullScreen) {
                     let hasFixedPos = c.derivedConfig.windowPositionX != nil && c.derivedConfig.windowPositionY != nil
                     // We're dispatching this async because otherwise the lastCascadePoint doesn't
-                    // take effect. Our best theory is there is some next-event-loop-tick logic
-                    // that Cocoa is doing that we need to be after.
-                    Self.applyCascade(to: window, hasFixedPos: hasFixedPos)
+                    // take effect after positioning in `showWindow`. Our best theory is there is
+                    // some next-event-loop-tick logic that Cocoa is doing that we need to be after.
+                    DispatchQueue.main.async {
+                        Self.applyCascade(to: window, hasFixedPos: hasFixedPos)
+                    }
                 }
             }