From 579d6f7b5c65dfc8aa7719919d9ade2929c5eada Mon Sep 17 00:00:00 2001 From: Marlon Kranz Date: Thu, 17 Sep 2026 15:37:39 +0200 Subject: [PATCH] fix(frame): keep launcher edge-hover on the Top layer (#3453) Opening the launcher by hovering the frame edge requested the Overlay layer via CompositorService.framePeerSurfacesUseOverlayForScreen(), which resolves to whether the frame is configured for the screen and is true in normal use. DankLauncherV2ModalConnected's frameOwnsConnectedChrome requires the Top layer, so the overlay request silently dropped connected-chrome anchoring: the launcher opened dead-centered with a different animation instead of emerging from the configured frame side. The keybind/bar-button path already opens on the Top layer by passing no overlay argument. The edge-hover trigger only runs in connected frame mode to begin with (gated by usesConnectedFrameChromeForScreen in this file's own eligible check), so there's no case where it needs standalone/overlay behavior. Match the keybind path. --- quickshell/Modules/Frame/FrameLauncherHoverZone.qml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/quickshell/Modules/Frame/FrameLauncherHoverZone.qml b/quickshell/Modules/Frame/FrameLauncherHoverZone.qml index 288c25510..fd1ac5d33 100644 --- a/quickshell/Modules/Frame/FrameLauncherHoverZone.qml +++ b/quickshell/Modules/Frame/FrameLauncherHoverZone.qml @@ -43,7 +43,7 @@ Variants { if (launcherOpen || _openedForCurrentHover) return; _openedForCurrentHover = true; - PopoutService.openDankLauncherV2(CompositorService.framePeerSurfacesUseOverlayForScreen(zoneLoader.modelData), true); + PopoutService.openDankLauncherV2(false, true); } screen: zoneLoader.modelData