Skip to content

e-stepper: the divider is always in view, and no second scroll bar - #156

Merged
martin-henz merged 3 commits into
mainfrom
e-stepper-divider-visible
Oct 9, 2026
Merged

martin-henz merged 3 commits into
mainfrom
e-stepper-divider-visible

Conversation

@martin-henz

@martin-henz martin-henz commented Oct 9, 2026 •

Copy link
Copy Markdown
Member

Measured in the deployed playground (Python §3, stacked layout, 676px-high window):

  • The bar was 0px high. The divider between the program and the environment (which sets how much of the tab each takes) was a flex item with the default flex-shrink: 1; the panes below it were taller than the tab, so it was the one thing squeezed. It is now flex: 0 0 auto, and sits above the arrows from the program (z-index), so they pass under it.
  • The panes overflowed the tab by ~120px (program pane 240px + diagram least height 240px > the space). That overflow made the host's side-content-text panel scroll. The program pane now leaves room for the divider and for the diagram's least height (80px, was 240px, in a stacked tab) at the tab's current height, so it can no longer be dragged taller than the tab, taking the divider out of view with nothing to drag back.
  • The tab overflowed its panel by ~21px, which made the card around it scroll too: two scroll bars. The tab went down to the window's bottom less a fixed 16px, but the margin on the tab (15px) and on its panel (6.4px) come on top of the panels' own paddings. The room is now the sum of the bottom margins, paddings and borders of the tab and every container around it.

Checked live: with these changes applied to the page, no container around the tab overflows, and the divider is 6px high. Tests: dragging far up/down in a stacked tab keeps the divider and the minimum heights; the room left below the tab follows the containers' styles; the stylesheet keeps the divider unshrinkable and above the arrows.

🤖 Generated with Claude Code

In a stacked tab that is short, the horizontal divider (a flex item that could
shrink) was squeezed to nothing between the fixed-height program pane and the
diagram's least height.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@changeset-bot

changeset-bot Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 8c31077

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

…der it

In a stacked tab the program pane could be dragged taller than the tab,
pushing the divider (and the diagram) out of view with nothing to drag back.
The pane now leaves room for the divider and the diagram's least height. The
divider also sits above the arrows from the program.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@martin-henz martin-henz changed the title e-stepper: the divider between the panes cannot shrink away e-stepper: the divider between the panes is always in view Oct 9, 2026
…nd it

The tab went down to the bottom of the window less a fixed 16px, but the host's
panels around it add about 22px more of margin and padding (and 16px of their
own), so the tab overflowed its panel and the panel around that: two scroll
bars. The room is now worked out from the containers' styles.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@martin-henz martin-henz changed the title e-stepper: the divider between the panes is always in view e-stepper: the divider is always in view, and no second scroll bar Oct 9, 2026
@martin-henz
martin-henz merged commit 457850a into main Oct 9, 2026
2 checks passed
@martin-henz
martin-henz deleted the e-stepper-divider-visible branch October 9, 2026 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant