Fix the music bar progress bar not spanning full width on desktop #19
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/music-bar-progress-full-width"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The other half of "desktop music player is broken," missed by the queue-popup fix — the compact bar's own internal layout was also wrong.
#trackProgressis.musicBarPanel's first child inside its 3-column grid (.musicBarPanelTrack/.musicBarPanelTransport/.musicBarPanelSide), but never had agrid-columnof its own. Auto-placement dropped it into column 1 of row 1 like any other item — squeezing it to that column's width and wrapping.musicBarPanelSideonto a second row underneath, instead of spanning the full bar with everything else in one row below it (which.musicBarProgressTrack's own existing comment already described as the intent). Easy to miss with no track loaded, since.musicBarPanelTrack's minimal placeholder content still left column 1 wide enough that the squeeze didn't look obviously broken.Fix:
.musicBarProgressTrack { grid-column: 1 / -1; }— spanning row 1 pushes every sibling after it into row 2 across the full width automatically, no changes needed to any of them.Test plan
npm run typecheck(client) — cleannpm run build(client) — cleaninitMusicBaragainst a synthetic reproduction of the real Shell markup + real compiled CSS, a fake track set so.musicBarPanelTrackhas realistic content.getBoundingClientRect()confirmed the progress bar's width exactly matches.musicBarPanel's own content width (not just the viewport), its bottom sits at or above every other row's top, and the other three elements' vertical ranges genuinely overlap each other (not just similartop, whichalign-items: centerlegitimately varies by content height) — one shared row below, in the original left-to-right order.🤖 Generated with Claude Code