implementation
Implement in your agent
# Implement Toast in your agent ## Objective Implement Toast for this verified behavior: A brief nonblocking message that appears after an event and may disappear after enough reading time. ## Prerequisites - Inspect the repository, design system, and existing tests first. - Preserve unrelated changes and keep the file scope bounded. - Confirm that Toast matches the need before writing code. ## Required behavior - The transient message may disappear after enough reading time and never blocks a critical decision. - A live region announces new status only when the update is important and not already focused. ## States to cover - Toast hidden — Toast hidden - Toast visible — Toast visible ## Accessibility - The primary control or named region for Toast has a stable accessible name from visible text or an explicit programmatic label; placeholder text and tooltips are not names. - The toast never steals focus on arrival; an optional action becomes reachable without disrupting the current task. - It expires after sufficient time, pauses for interaction, and can be dismissed explicitly without requiring action. - Tab reaches a toast action only through normal order - Escape dismisses the focused toast when supported ## Non-goals - The message contains critical recovery instructions - A decision or form error must remain visible ## Acceptance criteria - The toast never carries a critical decision - Arrival does not move focus - Reading time pauses during interaction - Stacked messages and their actions remain usable
sha256:962d745d5e4974f06f60f90aad43b179b583da956b7251a860f2a43cd9d6382e