Every control in the transport footer is a 34px pill: the on/off toggle, the count-in select, the meter select, Grid, the rate segment. The click volume is not. It is a 116px horizontal slider with a percentage after it, sitting on the same line, and nothing in the row shares an edge with it.
It is also the widest single item in the cluster, so when the options panel wraps it is the first thing pushed onto a line of its own, where it reads as a stray control rather than part of the group.
Why it matters beyond looking untidy
The click cluster is about half the width of the whole strip, and a 116px slider is a meaningful share of that. The footer runs out of width on a laptop before anything else does (#625), so the widest control in the widest cluster is worth looking at.
Constraints
- The level has to stay readable. A volume you can only learn by moving the fader is one you cannot match between sessions, which is why the percentage is on screen today.
#t-metro-vol is read by the prefs restore, the K key path and the export click render. Whatever replaces the layout should keep the same input element rather than rebuild it.- A fader that opens over the footer has the same clipping problem as anything else in
.footer-clusters, which is overflow-x: auto.
Every control in the transport footer is a 34px pill: the on/off toggle, the count-in select, the meter select, Grid, the rate segment. The click volume is not. It is a 116px horizontal slider with a percentage after it, sitting on the same line, and nothing in the row shares an edge with it.
It is also the widest single item in the cluster, so when the options panel wraps it is the first thing pushed onto a line of its own, where it reads as a stray control rather than part of the group.
Why it matters beyond looking untidy
The click cluster is about half the width of the whole strip, and a 116px slider is a meaningful share of that. The footer runs out of width on a laptop before anything else does (#625), so the widest control in the widest cluster is worth looking at.
Constraints
#t-metro-volis read by the prefs restore, the K key path and the export click render. Whatever replaces the layout should keep the same input element rather than rebuild it..footer-clusters, which isoverflow-x: auto.