An open source design system that's fully customizable and agent ready
TypeScript
spec(AST-086): identical same-frame repeats are one message; no busy start after its outcome (#8102)
Cindy Zhang34056d848e34
diff --git a/docs/specs/AST-086-status-announcements/spec.md b/docs/specs/AST-086-status-announcements/spec.mdindex 6681061e59..dfeee04b8e 100644--- a/docs/specs/AST-086-status-announcements/spec.md+++ b/docs/specs/AST-086-status-announcements/spec.md@@ -85,13 +85,14 @@ announcement channel.the shown words.- **FR8 — Indicators inside an owner are silent.** A visual indicator composedinside a component that owns the task, such as a Spinner in a busy control,- announces nothing and carries no live role. The owning component announces its busy state once per busy start (FR6), through the channel or through a persistent region that FR3 allows.+ announces nothing and carries no live role. The owning component announces its busy state once per busy start (FR6), through the channel or through a persistent region that FR3 allows. A busy start is not announced after the same operation's outcome has been announced; when the outcome announces first, the pending busy announcement is dropped.A standalone indicator is its own owner and follows FR2.- **FR9 — One shared channel per document.** The channel is one polite and oneassertive region per document. They are created empty, stay mounted for thedocument's lifetime, and clear their text shortly after each announcement sostale text does not linger. Messages written to a region before the previousone is exposed are joined in order into one announcement; none is dropped. An+ identical message repeated within the same frame is one message (FR6). Anempty message clears the region, including messages joined but not yetexposed.`useAnnounce` is the public way to reach it.@@ -210,6 +211,9 @@ announcement channel.announce their own content.- `useAnnounce`: messages written in the same frame are joined instead of thelast one replacing the others (FR9).+- `useAnnounce` collapses an identical message repeated in the same frame into+ one (FR9), and busy owners drop a pending busy announcement once the same+ operation's outcome has announced (FR8).- `spec:AST-037` FR9 (Timer adds no unsolicited live region) already conforms.- Consumer tests that query these elements by `status` or `alert` role change.Release notes name each affected component.@@ -223,8 +227,8 @@ announcement channel.| FR5 | Channel routing tests | Error, warning, success, loading | Routing an error to polite, or a success to assertive, fails || FR6 | StrictMode and rerender tests on the channel spy | Busy start, repeated rerender, same-value update, new occasion | Two announcements for one occasion, or none for a new one, fails || FR7 | Accessibility-tree check of the visible message | FieldStatus attached/detached, toast card | Hiding the visible text or a word mismatch fails |-| FR8 | Shared test: no live role inside a busy owner; channel spy on the owner | Busy TextInput, Selector, Switch thumb, ChatMessageList loader, busy CommandPalette (region inside its dialog) | A composed indicator with a live role or its own announcement, or a busy owner that announces nothing, fails |-| FR9 | `useAnnounce` tests | First use, many components, region removed, server render, two messages in one frame, clear after a joined message | A second region pair, stale text after the clear delay, a dropped same-frame message, or a joined message surviving a clear fails |+| FR8 | Shared test: no live role inside a busy owner; channel spy on the owner | Busy TextInput, Selector, Switch thumb, ChatMessageList loader, busy CommandPalette (region inside its dialog), operation that settles before its busy announcement is exposed | A composed indicator with a live role or its own announcement, or a busy owner that announces nothing, fails, or a busy start announced after its outcome, fails |+| FR9 | `useAnnounce` tests | First use, many components, region removed, server render, two messages in one frame, clear after a joined message, the same message twice in one frame | A second region pair, stale text after the clear delay, a dropped same-frame message, or a joined message surviving a clear fails, or an identical same-frame repeat announced twice, fails || FR10 | Accessibility-tree check with a Dialog open | Info and error toast shown over an open Dialog | A toast that reaches only the body-level channel, or no exposed live container, fails || FR11, FR12 | Helper and component tests | EmptyState present at page load, server-rendered, inserted later, text changed, hidden and shown again, brought in by a client-rendered route change, inside a chat log, empty Selector panel open at page load, server-rendered message inserted by client navigation, message inserted after first render but before the document finishes loading (silent) | Announcing at page load or during a server render (other than an announcement-only message), missing a later insertion or a server-rendered message inserted by client navigation, a client-rendered route change, or an empty Selector panel at page load, repeating one occasion, or also using the channel inside a live container fails || FR12 (server) | Server-safe component boundary check plus a server render of each adopter | EmptyState rendered on the server and hydrated | An adopter that fails the boundary check, or emits an announcement or live role from a server render, fails |