UI: card hover preview disappears immediately after configured delay fires

[matthewevans]

Reported behavior

After setting the card view timer in settings to 250ms, the expanded card preview appears but then disappears after only another ~quarter second. The preview should remain visible until the cursor leaves the card.

Expected

Card preview appears after the configured delay and stays visible until the user moves away.

Actual

Card preview appears after the configured delay but auto-dismisses after approximately the same duration again.

Source

https://discord.com/channels/1485498006781427802/1512159219548295228/1512159219548295228

---

_{report_id: discord:1512159219548295228:1512159219548295228:0 · via bug-triage}

[mike-theDude]

Triage

Area: frontend · Priority: p4-ui-polish · Status: confirmed

Reported behavior: With the card-view timer set to 250ms, the expanded card preview appears after the delay but then auto-dismisses after roughly another quarter second, instead of staying up until the cursor leaves the card.

Parser/runtime assessment: This is purely a frontend hover-preview timing bug — no card data or engine rules are involved. The configured delay value appears to be applied to both the show timer and a dismiss timer, so the preview is torn down one delay-interval after it opens rather than persisting for the duration of the hover. The owner is the React hover-preview component's timer lifecycle. (Reclassifying priority from p3-card-specific, which was auto-applied — this is a display/UX-only defect, not a card bug.)

Next step: Audit the hover-preview show/hide timer logic so the configured delay only gates appearance, not dismissal.

[mike-theDude]

Reviewed against current main: the configured hover latency now gates only initial preview appearance; dismissal is driven by hover-out or outside interaction. uiStoreHoverLatency.test.ts covers delayed appearance and cancellation, while usePreviewDismiss.test.tsx verifies that remaining over the card or preview keeps it open. The current behavior satisfies the report; please close the issue.

[matthewevans]

Closing per mike-theDude's triage above — verified fixed/resolved on current main. If this still reproduces on a current build, please reopen with a fresh repro.