Some notices can never be dismissed in the CLAP plugin — the Dismiss button falls outside a fixed-size editor that cannot be widened

[ErwanLegrand]

What happens

In the CLAP plugin, some notices can never be dismissed. The Dismiss button sits beyond the right
edge of the editor, and the editor cannot be widened. Since nothing else removes a notice, the row
stays for the lifetime of the plugin instance, permanently occupying part of a screen that already
cannot show every FR-UI-020 element at once.

Observed in Reaper on the reference machine during FR-UI-070's manual run (2026-08-27), step 14.

Cause — four choices, each defensible alone

1. The row does not wrap. crates/namir-ui/src/notices.rs:28 lays each notice out as
   ui.horizontal, label first and button after. An egui horizontal layout does not wrap, so a long
   label pushes the button past the edge.
2. The editor cannot be resized. crates/namir-clap/src/gui.rs:87 fixes GUI_WIDTH/GUI_HEIGHT
   at 960x640 and :196 returns can_resize() == false, deliberately — FR-CLAP-110 (host-driven
   resize) is a Should that was scoped out. So the standalone's escape hatch, widening the window,
   does not exist.
3. Notices never expire. push_notice appends to an unbounded Vec in both shells
   (crates/namir-app/src/host.rs:208, crates/namir-clap/src/shared.rs:212) and Dismiss is the
   only removal path (:456 / :220). No expiry, no severity-based timeout, no cap.
4. The text is about twice as long as it needs to be, because the code and message are rendered
   twice on several paths — filed separately as the duplication issue.

Nobody chose the outcome; it is the composition. Notably (4), which looks like a presentation defect
in isolation, is what makes (1) bite.

Fix

Either half prevents it:

• Pin Dismiss so it is always on screen — a right-to-left layout for the button, or draw it before
  the label.
• Let the label wrap or truncate with the full text on hover.

Bounding or expiring the notice list (3) is a separate improvement worth considering on its own: an
unbounded list of undismissable rows can in principle consume the whole editor.

Evidence

docs/manual-tests/fr-ui-070-non-modal-error-notices.md, executed run, finding 7 — and step 6 of the
same script passes in the standalone, where the button is reachable, which isolates the cause to the
fixed editor rather than to the dismissal logic.

[ErwanLegrand]

FIXED — all four contributing causes, across M14 (0a993da) and #145 (66c876c).

(1) The row. render_one lays the row out right-to-left, so the Dismiss button is placed against the panel's right edge before the text is measured — its position cannot depend on the text's length (crates/namir-ui/src/notices.rs:127-131). The label then wraps inside whatever is left. The scroll area is .auto_shrink([false, true]) so a narrower area cannot move the button back inside the text's reach.

Asserted at the real geometry: a_long_notice_keeps_its_dismiss_button_reachable_in_a_960x640_editor. render_one was split out of render specifically so the test finds the button's rectangle through the real layout code — the first draft measured a hand-copied second layout, found a plausible rectangle belonging to a row render had never drawn, and its synthetic click landed on nothing.

(3) The list. namir_ui::push_deduplicated caps the list at MAX_NOTICES by dropping the oldest, and both shells now push through it (crates/namir-app/src/host.rs:608, crates/namir-clap/src/shared.rs:345) rather than appending to an unbounded Vec. A cap rather than a timer, deliberately — the module doc records that a notice vanishing on its own is the "I never saw what went wrong" failure.

(4) The doubling — #39, fixed in the same M14 pass.

(2) is unchanged and no longer needs to change: the editor is still fixed at 960x640 with can_resize() == false, and the fix works at that geometry rather than depending on a wider one.

#145 also closed a second axis this issue did not have, and which M14's own fix created: the remedy line doubled every row's height, so the cap of sixteen bounded the list's length without bounding the space it takes, and a full list clipped its last rows off the bottom of the same editor. 66c876c bounds the scroll area vertically — "the half of #42 nobody had looked at".

---

Generated by Claude Code