What goes wrong
#480 added toggles for the three panels around the mixer, so any one of them can be put away when the lane stack runs short. That works, but it stops short of the thing people actually want at that moment, which is the mixer and nothing else.
Collapsing all three still leaves the library holding its column down the left. That is the largest single thing on screen that is not the mixer, so clearing the panels without it barely changes what you see. Getting to a bare mixer means pressing Analysis, Sections and Timeline in the toggles row, then finding the sidebar collapse button somewhere else entirely, and pressing that too. Four presses in two places, and four more to put it all back.
Who it affects
Anyone on a small screen, which is the case #480 exists for. At 1366x768 with six stems the lane stack needs 432px and gets 370. The panels give some of that back, the library gives back more, and there is no single control that asks for both.
What a fix has to handle
- One press to clear everything, one press to bring it back
- Not introducing a fourth piece of state. The three panels already keep a class on
.app and a flag in localStorage each, and the sidebar keeps its own pair. Anything that tracks "is everything collapsed" separately will disagree with the others the first time the library is collapsed from its own button instead
- Staying correct when the panels or the sidebar are moved from their existing controls
setSidebarCollapsed currently lives inside a function scope in catalog.js, and setCatalogView writes the same localStorage key by hand without updating the collapse button's aria-expanded. A second writer reproducing that pair is how it drifts- A new label is a user-facing string, so it needs keys in all ten language tables per
.claude/rules/i18n.md
What goes wrong
#480 added toggles for the three panels around the mixer, so any one of them can be put away when the lane stack runs short. That works, but it stops short of the thing people actually want at that moment, which is the mixer and nothing else.
Collapsing all three still leaves the library holding its column down the left. That is the largest single thing on screen that is not the mixer, so clearing the panels without it barely changes what you see. Getting to a bare mixer means pressing Analysis, Sections and Timeline in the toggles row, then finding the sidebar collapse button somewhere else entirely, and pressing that too. Four presses in two places, and four more to put it all back.
Who it affects
Anyone on a small screen, which is the case #480 exists for. At 1366x768 with six stems the lane stack needs 432px and gets 370. The panels give some of that back, the library gives back more, and there is no single control that asks for both.
What a fix has to handle
.appand a flag in localStorage each, and the sidebar keeps its own pair. Anything that tracks "is everything collapsed" separately will disagree with the others the first time the library is collapsed from its own button insteadsetSidebarCollapsedcurrently lives inside a function scope incatalog.js, andsetCatalogViewwrites the same localStorage key by hand without updating the collapse button'saria-expanded. A second writer reproducing that pair is how it drifts.claude/rules/i18n.md