Skip to content

The open tab's own bars stay at the top too - #176

Merged
davidackerman merged 1 commit into
mainfrom
sticky-bars
Oct 29, 2026
Merged

davidackerman merged 1 commit into
mainfrom
sticky-bars

Conversation

@davidackerman

Copy link
Copy Markdown
Collaborator

The open tab's own bars stay at the top of the dashboard's column as it scrolls, below the dashboard's tabs, in both modes:

  • Processing: the Apply bar ("Steps for all models"), then the Input normalization / Postprocessing tabs.
  • Finetune: the Annotation Crops / Training tabs.

Each sticks below the bars above it. Their offsets are those bars' heights, kept up to date by main.js stackStickyBars() in --tabs-h and --apply-h, because the tabs wrap onto two lines in a narrow column. The Apply bar was already sticky at the top of the column, where the dashboard's tabs have been since #173, so it slid under them.

Checked in a headless browser on the built app: scrolled, the tabs sit at 63–165 px, the Apply bar at 165–217 px and the Processing sub-tabs at 217–257 px; the Finetune sub-tabs sit at 165–205 px. vitest 599 passed; the dashboard page tests pass.

https://claude.ai/code/session_01EzWMS4pG3tm1ZtvKULfSfW

The Processing tab's Apply bar and its Input normalization / Postprocessing
tabs, and the Finetune tab's Annotation Crops / Training, stay in view as the
column scrolls, each below the bars above it. Their offsets are the heights
of those bars (main.js stackStickyBars keeps them in --tabs-h and --apply-h),
since the tabs wrap with the column's width. The Apply bar was sticky at top
0, where the dashboard's own sticky tabs now are, so it slid under them.

Claude-Session: https://claude.ai/code/session_01EzWMS4pG3tm1ZtvKULfSfW
@davidackerman
davidackerman marked this pull request as ready for review October 29, 2026 05:41
@davidackerman
davidackerman merged commit 3162bff into main Oct 29, 2026
7 checks passed
@davidackerman
davidackerman deleted the sticky-bars branch October 29, 2026 05:41
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