Bug: Tabbed and stacked groups that contain a split show windows on top of each other

Open
  • Is something wrong?
#566 0 comments 0 reactions 0 assignees View on GitHub

@mattchristenson is already working on this.

Since Sep 30, 2026.

  • #571 by @mattchristenson — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
desktop

Research direction

Run sandbox/run-suite.sh 16 17 to reproduce the failures in scenarios/17_stack_tab_switching.py and scenarios/16_tabbed_edge_resize.py. Read those scenarios to learn the expected tabbed/stacked behaviour. Note linked PR #571 already implements a fix, so the work is under way.

Written by the indexing model from the issue text.

Description

Problem. A tabbed or stacked group can hold a container, e.g. after Super+Z/Super+V (split) inside a tab, or when a split is toggled to tabbed/stacked. Such a member is handled as if it weren't there:

  • It has no tab or row. A tab group shows tabs only for its windows, and there is no tab to click to reach the split.
  • Stacks fall back to the cascade. A stack holding a split has no title list (P15 adds one only when every member is a window), so it cascades: the split is drawn over the other windows, with only their title bars peeking out above it.
  • Only one window of the split is raised. When a window in the split gets focus, only that window is raised. The group's other member stays on top of the split's other windows and shows through where they should be.

a split in a stack is drawn over the other window
with a split tab active, the other tab shows through

Desired outcome. A container in a tabbed or stacked group is a member like a window. It has a tab (or a row in the stack's title list) showing the title of the window last used in it, and how many more windows it holds. Clicking the tab goes to that window. While it is the member shown, all of its windows are in front of the group's other members. The member shown is always shown whole, and the others are fully hidden.

Acceptance criteria.

  • TABBED[W1, HSPLIT[W2, W3]]: two tabs. Clicking the split's tab focuses W2 or W3, and both show, with W1 fully hidden behind them. Clicking W1's tab hides the split behind W1.
  • STACKED[W1, HSPLIT[W2, W3]]: a title list with two rows (no cascade), the same behaviour.
  • Focus moving into the split by keyboard (Super+H/J/K/L) or by clicking one of its windows shows the whole split at once, with no other tab showing through in between.
  • The active tab is highlighted for the split too.
  • With title bars turned off (showtab-decoration-enabled), stacks keep the cascade as before.

Reproduction: scenarios/17_stack_tab_switching.py (17.11, 17.12) and scenarios/16_tabbed_edge_resize.py under the watcher (sandbox/run-suite.sh 16 17).

Dominant language
JavaScript
Stars
1.3k
Forks
112
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from forge-ext/forge

All issues in forge-ext/forge

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.