You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The entry form pane now scrolls like a proper scroll container. Scrolling a
long form — especially one with a read-only block taller than the pane, such as
a large group's member list — previously only worked with the arrow keys, and
only by moving focus from field to field. Now the mouse wheel, PageUp/PageDown, and dragging the scrollbar move the viewport directly,
independent of which field is focused, and the scrollbar thumb tracks the
scroll position so it moves as you go. In particular, after scrolling to the
bottom you can always scroll back up again (previously the keys were swallowed
by whatever field focus had landed on — "no getting back up"). The scrollbar
thumb no longer sits frozen while you page through a tall block.
Release builds no longer draw the footer one row too high, leaving the
bottom terminal row dead. Every released/deployed binary laid the whole UI
out one row short: the status line landed on the second-to-last row and the
entry form lost its bottom line. Builds run from cargo run were unaffected,
which is why it only ever showed on installed binaries. The cause is a rustc
miscompilation (reproduced on 1.93.1, 1.95.0 and 1.96.0, at every opt-level >= 1): Program::new passes the same screen extent by value to the
desktop / status-line / menu-bar factory closures, and the optimiser does not
re-materialise that argument between calls, so each factory saw whatever the
previous one had written into its own copy. The three factories now derive a
fresh Rect instead of mutating their parameter, which keeps the shared
argument intact. cargo test --release reproduces the old failure.