You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Right panel launcher letter shortcuts never fire: closed header-actions menu-popup stays mounted and trips the blocking-layer check #18602
It was the only [data-slot$="-popup"] element in the DOM. After temporarily renaming its data-slot, pressing T immediately opened Terminal 1 in the right panel, which confirms it's the cause.
Suggested fix: only treat open layers as blocking, e.g. match [data-open] / exclude [data-closed] (and/or skip elements inside a hidden positioner) in LAUNCHER_SHORTCUT_BLOCKING_LAYERS. The same selector is also used for the rightPanel.new handler on main, so that path is probably affected too.
Impact
Minor bug or occasional failure
Version or commit
Desktop 0.0.45 (blocking-layer selector is unchanged on main @ 58d2532)
Environment
macOS 26.6.2 (arm64), T3 Code (Alpha) desktop app
Workaround
Click the launcher row (or Tab to it and press Enter).
Related but different cause: #13427 (non-Latin layouts / focus).
Thanks for the detailed trace. This is the same root cause already tracked in #13403: the chat header actions MenuPopup stays mounted while closed, so the unguarded menu-popup entry in the launcher's blocking-layer selector always matches and the launcher letters (T, B, F, M…) never fire. That issue is confirmed and accepted.
The fix for the launcher half is in open PR #18132, which only treats overlays as blocking while they're open. Closing this as a duplicate of #13403; please follow along there. Until it lands, clicking the launcher row (or Tab + Enter) works.
Activity
juliusmarminge commentedon Oct 12, 2026
Note
Grok responding on behalf of Julius.
Thanks for the detailed trace. This is the same root cause already tracked in #13403: the chat header actions
MenuPopupstays mounted while closed, so the unguardedmenu-popupentry in the launcher's blocking-layer selector always matches and the launcher letters (T, B, F, M…) never fire. That issue is confirmed and accepted.The fix for the launcher half is in open PR #18132, which only treats overlays as blocking while they're open. Closing this as a duplicate of #13403; please follow along there. Until it lands, clicking the launcher row (or Tab + Enter) works.