Skip to content

fix(ui): pin the stats header above the scroller - #2

Merged
kolebayev merged 2 commits into
devfrom
kolebayev/header
Aug 21, 2026
Merged

kolebayev merged 2 commits into
devfrom
kolebayev/header

Conversation

@kolebayev

Copy link
Copy Markdown
Owner

Summary

The Stats tab's header — the listening-time title, its blurb and the Copy
Snapshot button — sat inside the scrolling pane, so it slid away with the
cover wall. It now sits above the scroller and stays put.

Changes

  • StatsView splits into a fixed header (shrink-0 border-b bg-background)
    and a scrolling body holding the cover wall, facts strip, treemap and
    rankings.
  • Root switches to flex h-full flex-col; h-full rather than flex-1
    because the tab wrapper in App.tsx is a plain block, the same reason
    EmptyState uses it.
  • Body top padding trimmed pt-10 → pt-8 now that the header is out of it.

Test plan

  • npm run typecheck — clean.
  • Not exercised against a device: no iPod fixture mounted, so the Stats tab
    was not opened in the running app.

Note: this branch forked from main, which is ahead of dev, so the PR also
carries docs: rewrite the readme for users (#1).

The title and Copy Snapshot lived inside the scrolling pane, so they
slid away as soon as the cover wall moved.
@kolebayev
kolebayev merged commit 032f255 into dev Aug 21, 2026
4 checks passed
kolebayev added a commit that referenced this pull request Aug 21, 2026
feat(ui): sort the track list by column heading

StatsView conflicted with the pinned header from #2: both branches
replaced the pane's `flex-1` root because the tab wrapper is a plain
block. The header split already roots at `flex h-full flex-col` and
moved the scroller inside, so that structure wins and only the
reasoning from this branch's comment is kept.
@kolebayev
kolebayev deleted the kolebayev/header branch August 21, 2026 14:29
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