navigate_to_prev_item (navigate to previous sibling; shortcut: meta+shift+9) works normally in the new pane, but navigate_to_next_item (navigate to next sibling; shortcut: meta+shift+0) does not work in the new pane (Only effective on the leftmost pane).
Besides,
the next item (sibling) command, when invoked in pane 2 or later, affects pane 1.
reproduced in 4.3.2608241510 [beta, chrome-150, mac]
same issue, in 4.3.2608241856 [beta, chrome-150, mac]
Confirmed. Surprised that this bug has persisted for 2 weeks. Perhaps (optimistic take) there is some re-architecting happening for panes…
Still present in 4.3.2609122032 [beta, edge, win]
Also, unsurprisingly, navigate_to_prev_item has the same issue (affects pane 1 no matter which pane it is invoked from.)
Confirming that this issue is still present on my end as well. I reported this exact set of keyboard navigation and focus bugs directly to support over 40+ days ago (ticket #85782), so it’s concerning to see them still affecting daily workflows across production/beta versions.
Panes is such a core feature for productivity, but these focus and navigation glitches make multi-pane setups really frustrating to rely on. At the moment I don’t use PANES…
Hoping the team can prioritize a fix soon ! It shouldn’t take that long…
@ksenia ?