test(desktop): a panel dragged narrower stops at its minimum, and closes only past its threshold #477

2026-10-19T08:27:11Z

rvnminers-A-and-N commented

2026-10-19 08:27:11 +00:00

Part of #98 (resizable panels: minimum widths and the closing threshold), as agreed with @excho0 on #117 and #99.

For the conversation-history and topology handles, in LTR (English) and RTL (Hebrew), one continuous drag takes each panel to raw widths of:

240 px: the panel holds open at its 280 px minimum (aria-valuenow);
212 px: still open at 280, just inside the closing threshold (minimum − 72);
200 px: past the threshold, so the panel closes.

Which way is narrower follows the writing direction:

the history panel narrows toward the start edge (left in LTR, right in RTL);
the topology panel narrows toward the end edge.

The handles are found by class, because their accessible names are translated in Hebrew. Without WebGL only the history panel is checked (CI draws WebGL in software, so both are checked there).

Verified locally against the built app under xvfb-run:

it passes in about 73 s;
with the threshold weakened from 72 to 20 px in WorkspacePage.tsx, it fails, so it pins the behaviour.

Test-only change.

Part of #98 (resizable panels: minimum widths and the closing threshold), as agreed with @excho0 on #117 and #99. For the conversation-history and topology handles, in LTR (English) and RTL (Hebrew), one continuous drag takes each panel to raw widths of: - **240 px:** the panel holds open at its **280 px minimum** (`aria-valuenow`); - **212 px:** still open at 280, just inside the closing threshold (`minimum − 72`); - **200 px:** past the threshold, so the panel closes. Which way is narrower follows the writing direction: - the history panel narrows toward the start edge (left in LTR, right in RTL); - the topology panel narrows toward the end edge. The handles are found by class, because their accessible names are translated in Hebrew. Without WebGL only the history panel is checked (CI draws WebGL in software, so both are checked there). **Verified locally** against the built app under `xvfb-run`: - it passes in about 73 s; - with the threshold weakened from 72 to 20 px in `WorkspacePage.tsx`, it fails, so it pins the behaviour. Test-only change.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Sisyphus/Sisyphus#477