From 52e7598da03603cf7ab61eadb51e1acb016d859c Mon Sep 17 00:00:00 2001 From: Levi Neuwirth Date: Fri, 24 Jul 2026 18:37:10 -0400 Subject: [PATCH] test(window): press the peer's own mode line in acc30c MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The round-2 peer press landed in the peer's CONTENT area, so it never reached `arm_window_drag` — the exact path Finding 5 names — and the case bit nothing. It now presses the peer's own mode-line row, where a single global drag slot is overwritten (and, since that lone window owns no boundary, cleared outright). Co-Authored-By: Claude Opus 5 (1M context) --- tests/bottom_panel_stage1_acceptance.rs | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/tests/bottom_panel_stage1_acceptance.rs b/tests/bottom_panel_stage1_acceptance.rs index f9acea1..e358351 100644 --- a/tests/bottom_panel_stage1_acceptance.rs +++ b/tests/bottom_panel_stage1_acceptance.rs @@ -1838,12 +1838,15 @@ fn acc30c_an_armed_drag_does_not_swallow_another_frontends_mouse_events() { "the peer's click reached its own window instead of being swallowed" ); - // …a peer press on a MODE-LINE row must not steal or clear the slot - // either — that press reaches the arming path, which a single global - // slot would let it overwrite. + // …a peer press on ITS OWN mode-line row must not steal or clear the + // slot either. That press reaches `arm_window_drag`, which a single + // global slot lets it overwrite — and the peer's lone window owns no + // boundary, so the write is an outright clear. The peer's mode line + // is the last row of its own single-window layout. + let peer_mode_line = u16::try_from(AREA_ROWS - 1).expect("row fits"); s.dispatch_mouse( other, - mouse(MouseEventKind::Down(MouseButton::Left), divider_row, 4), + mouse(MouseEventKind::Down(MouseButton::Left), peer_mode_line, 4), CellSize::new(ROWS, COLS), );