An open source design system that's fully customizable and agent ready
TypeScript
docs: consolidate + credit changesets for v0.5.0 (#5432)
Cindy Zhang2eb194f36be6
diff --git a/.changeset/a11y-table-pagination-both-labels.md b/.changeset/a11y-table-pagination-both-labels.mdindex e7b167503a..51cb4dd233 100644--- a/.changeset/a11y-table-pagination-both-labels.md+++ b/.changeset/a11y-table-pagination-both-labels.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] useTablePagination: with `position='both'` the two pagination `<nav>` landmarks now get distinct accessible names — "{label} (top)" above the table and "{label} (bottom)" below it (axe landmark-unique). Consumer-supplied `label` values are interpolated into both names; single-position labels are unchanged.+[fix] useTablePagination: with `position='both'` the two pagination `<nav>` landmarks now get distinct accessible names — "{label} (top)" above the table and "{label} (bottom)" below it (axe landmark-unique). Consumer-supplied `label` values are interpolated into both names; single-position labels are unchanged (#4692).@AKnassadiff --git a/.changeset/a11y-table-row-expansion-header.md b/.changeset/a11y-table-row-expansion-header.mdindex 4c95353214..e6cd49eb8f 100644--- a/.changeset/a11y-table-row-expansion-header.md+++ b/.changeset/a11y-table-row-expansion-header.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] Table useTableRowExpansion: the chevron gutter's column header now carries a visually hidden localized name ("Row expansion", key `@astryx.tableRowExpansion.columnHeader`) instead of an empty `<th>` (axe empty-table-header, WCAG 1.3.1 best practice). The gutter stays visually blank.+[fix] Table useTableRowExpansion: the chevron gutter's column header now carries a visually hidden localized name ("Row expansion", key `@astryx.tableRowExpansion.columnHeader`) instead of an empty `<th>` (axe empty-table-header, WCAG 1.3.1 best practice). The gutter stays visually blank (#5383).@cixzhangdiff --git a/.changeset/a11y-table-row-status-header.md b/.changeset/a11y-table-row-status-header.mdindex 101cf8eaf4..e79714d2f4 100644--- a/.changeset/a11y-table-row-status-header.md+++ b/.changeset/a11y-table-row-status-header.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] Table useTableRowStatus: the status gutter's column header now carries a visually hidden localized name ("Row status", key `@astryx.table.rowStatus.columnHeader`) instead of an empty `<th>` (axe empty-table-header, WCAG 1.3.1 best practice). The gutter stays visually blank.+[fix] Table useTableRowStatus: the status gutter's column header now carries a visually hidden localized name ("Row status", key `@astryx.table.rowStatus.columnHeader`) instead of an empty `<th>` (axe empty-table-header, WCAG 1.3.1 best practice). The gutter stays visually blank (#4693).@AKnassadiff --git a/.changeset/allow-multiselector-count-labels-to-be-customize-6kj4.md b/.changeset/allow-multiselector-count-labels-to-be-customize-6kj4.mdindex 4bdb80cd0e..2438b0bda6 100644--- a/.changeset/allow-multiselector-count-labels-to-be-customize-6kj4.md+++ b/.changeset/allow-multiselector-count-labels-to-be-customize-6kj4.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[component] Allow MultiSelector count labels to be customized+[component] Allow MultiSelector count labels to be customized (#4032)@Kevinjohndiff --git a/.changeset/api-contract-drift-docs-tjsk.md b/.changeset/api-contract-drift-docs-tjsk.mdindex 9800f28aa8..e127542ca4 100644--- a/.changeset/api-contract-drift-docs-tjsk.md+++ b/.changeset/api-contract-drift-docs-tjsk.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[docs] document missing API contract props across Button, Toast, ContextMenu, MoreMenu, Selector, Link, and Dialog (#4163)+[docs] document missing API contract props across Button, Toast, ContextMenu, MoreMenu, Selector, Link, and Dialog (#4315, part of #4163)@HelloOjasMutrejadiff --git a/.changeset/aspectratio-responsive-ratio.md b/.changeset/aspectratio-responsive-ratio.mdindex 2812e9bfd9..c3019b711e 100644--- a/.changeset/aspectratio-responsive-ratio.md+++ b/.changeset/aspectratio-responsive-ratio.md@@ -3,5 +3,5 @@'@astryxdesign/cli': patch----[feat] AspectRatio: emit `ratio` as a class-level declaration instead of a hard inline style, so the ratio can be overridden responsively: StyleX consumers pass an `aspect-ratio` rule via `xstyle` (including under `@media`/`@container` conditions), and plain-CSS/Tailwind consumers override `aspect-ratio` from their own unlayered rules, which beat the `astryx-base` cascade layer regardless of specificity. The mixed-gallery template's hero now switches 3:1 to 3:2 when the grid stacks with a one-line override on a single element, replacing the duplicated hero markup the fixed inline ratio previously forced (#2798)+[feat] AspectRatio: emit `ratio` as a class-level declaration instead of a hard inline style, so the ratio can be overridden responsively: StyleX consumers pass an `aspect-ratio` rule via `xstyle` (including under `@media`/`@container` conditions), and plain-CSS/Tailwind consumers override `aspect-ratio` from their own unlayered rules, which beat the `astryx-base` cascade layer regardless of specificity. The mixed-gallery template's hero now switches 3:1 to 3:2 when the grid stacks with a one-line override on a single element, replacing the duplicated hero markup the fixed inline ratio previously forced (#3883, closes #2798)@jiunshinndiff --git a/.changeset/badge-error-contrast-aa.md b/.changeset/badge-error-contrast-aa.mdindex 25c738638e..34b035a687 100644--- a/.changeset/badge-error-contrast-aa.md+++ b/.changeset/badge-error-contrast-aa.md@@ -3,6 +3,6 @@'@astryxdesign/cli': patch----[fix] neutral theme: darken the light-mode error red from `#e33f4a` to `#c9303a` so the filled `Badge variant="error"` label clears WCAG 2.1 AA. White on `#e33f4a` is 4.14:1 and the badge label is 12px/weight 500, so the 4.5:1 normal-text threshold applies rather than the 3:1 large-text allowance; `#c9303a` gives 5.29:1 while holding the hue (OKLCH H 21.9 -> 22.8, C 0.200 -> 0.189). StatusDot and the ProgressBar `--color-error` rebinding move with it — both are documented as tracking the badge fill so the dot and its badge read as one status language. Dark mode is untouched (dark text on `#ff705d`, 6.60:1). Adds `scripts/check-badge-contrast.test.mjs`, which resolves every theme's badge label/fill pair through `light-dark()`, `var()` indirection and alpha compositing, and holds all of them to 4.5:1.+[fix] neutral theme: darken the light-mode error red from `#e33f4a` to `#c9303a` so the filled `Badge variant="error"` label clears WCAG 2.1 AA. White on `#e33f4a` is 4.14:1 and the badge label is 12px/weight 500, so the 4.5:1 normal-text threshold applies rather than the 3:1 large-text allowance; `#c9303a` gives 5.29:1 while holding the hue (OKLCH H 21.9 -> 22.8, C 0.200 -> 0.189). StatusDot and the ProgressBar `--color-error` rebinding move with it — both are documented as tracking the badge fill so the dot and its badge read as one status language. Dark mode is untouched (dark text on `#ff705d`, 6.60:1). Adds `scripts/check-badge-contrast.test.mjs`, which resolves every theme's badge label/fill pair through `light-dark()`, `var()` indirection and alpha compositing, and holds all of them to 4.5:1 (#4446).@AKnassadiff --git a/.changeset/bottom-sheet-ime-escape-guard.md b/.changeset/bottom-sheet-ime-escape-guard.mdindex 58533d7092..df9daaa071 100644--- a/.changeset/bottom-sheet-ime-escape-guard.md+++ b/.changeset/bottom-sheet-ime-escape-guard.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] BottomSheet: a standalone sheet no longer dismisses when a CJK user presses Escape to cancel an in-progress IME composition. The browser fires that keydown before `compositionend`, so an Escape handler reading a bare `event.key` misread the composition cancel as a dismissal command and closed the sheet — losing whatever had been typed into a `purpose="form"` field inside it. The handler now early-returns on `isImeKeyEvent`, the same guard `Dialog` and `BottomSheetSwitcher` already carry, and claims the key first so the browser raises no close request of its own.+[fix] BottomSheet: a standalone sheet no longer dismisses when a CJK user presses Escape to cancel an in-progress IME composition. The browser fires that keydown before `compositionend`, so an Escape handler reading a bare `event.key` misread the composition cancel as a dismissal command and closed the sheet — losing whatever had been typed into a `purpose="form"` field inside it. The handler now early-returns on `isImeKeyEvent`, the same guard `Dialog` and `BottomSheetSwitcher` already carry, and claims the key first so the browser raises no close request of its own (#5322).@ernesttdiff --git a/.changeset/breadcrumb-current-non-color-indicator.md b/.changeset/breadcrumb-current-non-color-indicator.mdnew file mode 100644index 0000000000..af0230fd1b--- /dev/null+++ b/.changeset/breadcrumb-current-non-color-indicator.md@@ -0,0 +1,7 @@+---+'@astryxdesign/core': patch+---++[fix] `Breadcrumbs` marks the current item with semibold weight, not colour alone. The current crumb was distinguished only by `--color-text-primary` against its siblings' `--color-text-secondary`, which fails WCAG 1.4.1 (use of colour) and leaves the current position invisible to anyone who cannot separate the two tones (#4605, closes #4421).++@gonzoblascodiff --git a/.changeset/button-group-layer-arrow-keys.md b/.changeset/button-group-layer-arrow-keys.mdindex 5f99777711..931fbeea14 100644--- a/.changeset/button-group-layer-arrow-keys.md+++ b/.changeset/button-group-layer-arrow-keys.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] ButtonGroup: arrow keys pressed inside a member's open menu stay with that menu. A DropdownMenu renders its menu inline inside the group, so ArrowLeft and ArrowRight used to bubble to the group and move focus onto a sibling button while the menu was still open. The group's `elevation` is also reflected as `data-elevation` now, so a theme can target it.+[fix] ButtonGroup: arrow keys pressed inside a member's open menu stay with that menu. A DropdownMenu renders its menu inline inside the group, so ArrowLeft and ArrowRight used to bubble to the group and move focus onto a sibling button while the menu was still open. The group's `elevation` is also reflected as `data-elevation` now, so a theme can target it (#5355).@cixzhangdiff --git a/.changeset/calendar-initial-month-clamp.md b/.changeset/calendar-initial-month-clamp.mdindex 8d17384885..c843bf435b 100644--- a/.changeset/calendar-initial-month-clamp.md+++ b/.changeset/calendar-initial-month-clamp.md@@ -15,4 +15,4 @@ The initial month is now today clamped into the window: today when it is inside,otherwise whichever bound is nearest. An explicit `focusDate` or a selected valuestill wins, so nothing changes for callers that already say where to look. With`numberOfMonths={2}` a past window lands `max` in the right-hand pane, so neither-pane is entirely out of bounds.+pane is entirely out of bounds (#5306).diff --git a/.changeset/chatmessagelist-add-align-prop-for-top-aligned-l-xm43.md b/.changeset/chatmessagelist-add-align-prop-for-top-aligned-l-xm43.mdindex ebae48ff36..a2e2f5ad72 100644--- a/.changeset/chatmessagelist-add-align-prop-for-top-aligned-l-xm43.md+++ b/.changeset/chatmessagelist-add-align-prop-for-top-aligned-l-xm43.md@@ -3,7 +3,7 @@---[feat] ChatMessageList: add an `align` prop for top-aligned message lists-(#2572).+(#3933, closes #2572).- `align?: 'top' | 'bottom'` (default `'bottom'`). `'bottom'` keeps theexisting behavior: a flex spacer fills free space so a short conversationdiff --git a/.changeset/cli-integration-components-in-search.md b/.changeset/cli-integration-components-in-search.mdnew file mode 100644index 0000000000..d787288986--- /dev/null+++ b/.changeset/cli-integration-components-in-search.md@@ -0,0 +1,7 @@+---+'@astryxdesign/cli': patch+---++[fix] Unified search and build now include components contributed by integrations, so a component registered through an integration is findable and buildable alongside the built-in set instead of silently missing from both (#5259).++@andrskrdiff --git a/.changeset/cli-theme-targets.md b/.changeset/cli-theme-targets.mdindex e92d003b84..43dd1a6442 100644--- a/.changeset/cli-theme-targets.md+++ b/.changeset/cli-theme-targets.md@@ -2,5 +2,5 @@'@astryxdesign/cli': patch----[feat] CLI: `astryx theme targets` lists every component theming target — the `defineTheme` key, the class it paints, and the props and states it accepts — for one component or the whole system, with `--json` for lint and audit scripts. `astryx theme --help` now points at component overrides instead of reading as a build-tool menu. The listing and `theme build`'s override validation share one enumeration of the component docs, so neither can drift from the components.+[feat] CLI: `astryx theme targets` lists every component theming target — the `defineTheme` key, the class it paints, and the props and states it accepts — for one component or the whole system, with `--json` for lint and audit scripts. `astryx theme --help` now points at component overrides instead of reading as a build-tool menu. The listing and `theme build`'s override validation share one enumeration of the component docs, so neither can drift from the components (#5115).@cixzhangdiff --git a/.changeset/complex-component-contract-docs-tjsk.md b/.changeset/complex-component-contract-docs-tjsk.mdindex c7acbc8237..5ca7eb87c5 100644--- a/.changeset/complex-component-contract-docs-tjsk.md+++ b/.changeset/complex-component-contract-docs-tjsk.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[docs] document missing props across complex components (MultiSelector, Tokenizer, PowerSearch, Typeahead, Layout, DropdownMenu, HoverCard, Tooltip, Link, Lightbox) (#4163)+[docs] document missing props across complex components (MultiSelector, Tokenizer, PowerSearch, Typeahead, Layout, DropdownMenu, HoverCard, Tooltip, Link, Lightbox) (#4316, part of #4163)@HelloOjasMutrejadiff --git a/.changeset/content-component-contract-docs-tjsk.md b/.changeset/content-component-contract-docs-tjsk.mdindex 00a2df2ce5..fc01d6b516 100644--- a/.changeset/content-component-contract-docs-tjsk.md+++ b/.changeset/content-component-contract-docs-tjsk.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[docs] document the missing components prop on Markdown (#4163)+[docs] document the missing components prop on Markdown (#4319, part of #4163)@HelloOjasMutrejadiff --git a/.changeset/date-input-touch-clear-preventscroll.md b/.changeset/date-input-touch-clear-preventscroll.mdindex 2611e639cf..c8377ba9e3 100644--- a/.changeset/date-input-touch-clear-preventscroll.md+++ b/.changeset/date-input-touch-clear-preventscroll.md@@ -14,6 +14,6 @@ field.Measured on the iOS 26 simulator against the live docsite (DateInput —Clearable, page at scrollY 2055): synchronous focus → 0, deferred focus → 2055.`preventScroll` alone does not fix it; it is kept for the ordinary-scroll-into-view nudge, which is unwanted for the same reason.+scroll-into-view nudge, which is unwanted for the same reason (#5350).@imdreamrunnerdiff --git a/.changeset/datetimeinput-time-option-dropdown.md b/.changeset/datetimeinput-time-option-dropdown.mdindex b4f078c7bd..41b55cabd2 100644--- a/.changeset/datetimeinput-time-option-dropdown.md+++ b/.changeset/datetimeinput-time-option-dropdown.md@@ -4,6 +4,6 @@[feat] DateTimeInput: new `timeOptionInterval` prop adds a dropdown of preset times to the time field, at a cadence of `5 | 10 | 15 | 30 | 60` minutes (`60` gives the 12 AM - 11 PM list). The field becomes an APG combobox over a `listbox`: click or Alt+ArrowDown opens it, ArrowUp/ArrowDown move the active option, Enter picks, Escape closes, and typing moves the highlight to the closest option without filtering the list. `min`/`max` trim the options on the boundary date. Style the popup through the `date-time-input-time-listbox` and `date-time-input-time-option` theme targets.-Opt-in and additive: with `timeOptionInterval` omitted the time field keeps exactly its current behavior and gains no combobox semantics, so existing `getByRole('combobox')` queries still resolve to the date input. With the list closed the arrow keys keep stepping by `timeIncrement`.+Opt-in and additive: with `timeOptionInterval` omitted the time field keeps exactly its current behavior and gains no combobox semantics, so existing `getByRole('combobox')` queries still resolve to the date input. With the list closed the arrow keys keep stepping by `timeIncrement` (#4837).@AKnassadiff --git a/.changeset/dialog-responsive-interaction.md b/.changeset/dialog-responsive-interaction.mdindex 98803e84ca..62870f0609 100644--- a/.changeset/dialog-responsive-interaction.md+++ b/.changeset/dialog-responsive-interaction.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Clamp standard Dialog width to dynamic viewport space with token gutters, add safe-area/fullscreen sizing and fade-only fullscreen motion updates, add opt-in adaptive Dialog/BottomSheet recipes, and add explicit presentation comparison stories.+[fix] Clamp standard Dialog width to dynamic viewport space with token gutters, add safe-area/fullscreen sizing and fade-only fullscreen motion updates, add opt-in adaptive Dialog/BottomSheet recipes, and add explicit presentation comparison stories (#5352).-@rubycheung+@rubyycheungdiff --git a/.changeset/dropdown-menu-theme-fixes.md b/.changeset/dropdown-menu-theme-fixes.mdindex 522f44523b..ca6c6b8722 100644--- a/.changeset/dropdown-menu-theme-fixes.md+++ b/.changeset/dropdown-menu-theme-fixes.md@@ -4,6 +4,6 @@[fix] DropdownMenu: move the `dropdown-menu-indicator-icon` theme target onto the Icon element itself so a theme can restyle the submenu chevron's size and color directly.-The loading branch no longer carries the target — its `Spinner` has its own `astryx-spinner` target, matching Selector, MultiSelector and ComplexSelector.+The loading branch no longer carries the target — its `Spinner` has its own `astryx-spinner` target, matching Selector, MultiSelector and ComplexSelector (#4743).@athzdiff --git a/.changeset/field-contract-docs-tjsk.md b/.changeset/field-contract-docs-tjsk.mdindex 46e0ace4ef..b208a320d5 100644--- a/.changeset/field-contract-docs-tjsk.md+++ b/.changeset/field-contract-docs-tjsk.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[docs] document labelID and isGroupLabel props in Field (#4163)+[docs] document labelID and isGroupLabel props in Field (#4320, part of #4163)@HelloOjasMutrejadiff --git a/.changeset/fix-chat-bubble-token-alignment.md b/.changeset/fix-chat-bubble-token-alignment.mdindex f3fce05847..7785dbbe6f 100644--- a/.changeset/fix-chat-bubble-token-alignment.md+++ b/.changeset/fix-chat-bubble-token-alignment.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Chat: a token in a message bubble now sits on the line the way it does in the composer. `ChatTokenizedText` wraps each token in the same `inline-flex` / `vertical-align: middle` box `ChatComposerInput` uses, so a chip stops lifting off the text the moment the message is sent. Follows #5324, which fixed the composer half.+[fix] Chat: a token in a message bubble now sits on the line the way it does in the composer. `ChatTokenizedText` wraps each token in the same `inline-flex` / `vertical-align: middle` box `ChatComposerInput` uses, so a chip stops lifting off the text the moment the message is sent. Follows #5324, which fixed the composer half (#5402).@cixzhangdiff --git a/.changeset/fix-chat-token-alignment.md b/.changeset/fix-chat-token-alignment.mdindex 8d42229583..eb32cb44d9 100644--- a/.changeset/fix-chat-token-alignment.md+++ b/.changeset/fix-chat-token-alignment.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Chat: composer tokens no longer sit above surrounding text — `vertical-align` changed from `baseline` to `middle`, and `ChatComposerTokenElement` now uses a StyleX class instead of an inline style so consumers can override alignment without `!important`.+[fix] Chat: composer tokens no longer sit above surrounding text — `vertical-align` changed from `baseline` to `middle`, and `ChatComposerTokenElement` now uses a StyleX class instead of an inline style so consumers can override alignment without `!important` (#5324).@athzdiff --git a/.changeset/focus-trap-tab-outside.md b/.changeset/focus-trap-tab-outside.mdindex bfa6adcd20..856f08b0e0 100644--- a/.changeset/focus-trap-tab-outside.md+++ b/.changeset/focus-trap-tab-outside.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] useFocusTrap: Tab is only cancelled when focus is actually inside the trapped container. An open layer whose focus legitimately sits outside it — a listbox popup anchored to its own input, as in DateTimeInput, Typeahead, Selector and MultiSelector — no longer swallows Tab for the whole page, so keyboard users move to the next control on the first press. A trapped surface with no tabbable controls and focus on a `tabIndex={-1}` panel still keeps Tab inside it.+[fix] useFocusTrap: Tab is only cancelled when focus is actually inside the trapped container. An open layer whose focus legitimately sits outside it — a listbox popup anchored to its own input, as in DateTimeInput, Typeahead, Selector and MultiSelector — no longer swallows Tab for the whole page, so keyboard users move to the next control on the first press. A trapped surface with no tabbable controls and focus on a `tabIndex={-1}` panel still keeps Tab inside it (#5397).@cixzhangdiff --git a/.changeset/kbd-hotkeys-blank-client-hints-platform.md b/.changeset/kbd-hotkeys-blank-client-hints-platform.mdindex d7052a7dd7..4c3789adc4 100644--- a/.changeset/kbd-hotkeys-blank-client-hints-platform.md+++ b/.changeset/kbd-hotkeys-blank-client-hints-platform.md@@ -11,6 +11,6 @@ reporting `platform: ''` therefore committed to the client-hints branch and got`false` without ever reaching the fallback, so on macOS every `mod` combolistened for Ctrl and every `<Kbd>` drew Ctrl. Electron and other embeddersthat rewrite the app's user-agent identity ship exactly that. A blank platform-is now treated as unknown and falls through.+is now treated as unknown and falls through (#5325).@Astro-Handiff --git a/.changeset/layer-dismissal-stack.md b/.changeset/layer-dismissal-stack.mdindex e7495c39a1..0acd725897 100644--- a/.changeset/layer-dismissal-stack.md+++ b/.changeset/layer-dismissal-stack.md@@ -2,7 +2,7 @@'@astryxdesign/core': minor----[breaking] Overlays share one dismissal stack, so a single Escape dismisses exactly one layer. Every overlay used to own its own Escape listener, which meant one press could close a popover _and_ the Dialog hosting it, or a modal _and_ the modal it was opened from. `useLayerDismissal` replaces that with a single stack: the stack owns one listener, routes each press to the top-most layer, and suppresses the browser's own close-watcher so nothing dismisses twice. A layer declares what it does with a press via `escapeBehavior` — `close` (default) or `block`, for a `required` Dialog that must swallow the press without closing so nothing behind it dismisses either. Fixes a Tooltip inside a Dialog closing the Dialog rather than the tip, and a HoverCard trigger swallowing Escape whenever it merely had focus. Dismissals the browser starts on its own — the Android back gesture, the platform close watcher — still close a Dialog, and follow the same top-most rule. An Escape that cancels an in-progress IME composition dismisses nothing: the stack claims that press so the browser raises no close request of its own, and a close request that arrives mid-composition anyway is declined, so a CJK user backing out of a half-formed character no longer loses the layer and everything typed into it. One behavior change worth knowing about if you listen for Escape yourself: the stack claims a press with `preventDefault()` but deliberately leaves propagation alone, so a `keydown` listener on `window` now sees an Escape that a focus-trapped layer used to stop — with `defaultPrevented` already `true`, which is how to tell the stack has acted on it. Top-most is resolved from React-tree nesting (which survives portals) rather than DOM containment alone. A layer's place in that order is keyed to the layer's identity rather than to each registration, so a prop change that re-registers it — a Dialog whose `purpose` flips while it is open — never promotes it above the layers opened over it. Controlled layers follow their control state: a controlled `Tooltip` or `HoverCard` stays on the stack and takes the press like any other layer, but answers it by calling `onOpenChange(false)` rather than hiding itself — whether it actually closes is the caller's update to make, exactly as it has always been for `Dialog`.+[breaking] Overlays share one dismissal stack, so a single Escape dismisses exactly one layer. Every overlay used to own its own Escape listener, which meant one press could close a popover _and_ the Dialog hosting it, or a modal _and_ the modal it was opened from. `useLayerDismissal` replaces that with a single stack: the stack owns one listener, routes each press to the top-most layer, and suppresses the browser's own close-watcher so nothing dismisses twice. A layer declares what it does with a press via `escapeBehavior` — `close` (default) or `block`, for a `required` Dialog that must swallow the press without closing so nothing behind it dismisses either. Fixes a Tooltip inside a Dialog closing the Dialog rather than the tip, and a HoverCard trigger swallowing Escape whenever it merely had focus. Dismissals the browser starts on its own — the Android back gesture, the platform close watcher — still close a Dialog, and follow the same top-most rule. An Escape that cancels an in-progress IME composition dismisses nothing: the stack claims that press so the browser raises no close request of its own, and a close request that arrives mid-composition anyway is declined, so a CJK user backing out of a half-formed character no longer loses the layer and everything typed into it. One behavior change worth knowing about if you listen for Escape yourself: the stack claims a press with `preventDefault()` but deliberately leaves propagation alone, so a `keydown` listener on `window` now sees an Escape that a focus-trapped layer used to stop — with `defaultPrevented` already `true`, which is how to tell the stack has acted on it. Top-most is resolved from React-tree nesting (which survives portals) rather than DOM containment alone. A layer's place in that order is keyed to the layer's identity rather than to each registration, so a prop change that re-registers it — a Dialog whose `purpose` flips while it is open — never promotes it above the layers opened over it. Controlled layers follow their control state: a controlled `Tooltip` or `HoverCard` stays on the stack and takes the press like any other layer, but answers it by calling `onOpenChange(false)` rather than hiding itself — whether it actually closes is the caller's update to make, exactly as it has always been for `Dialog` (#4881).@freddymeta@cixzhangdiff --git a/.changeset/markdown-incremental-cache-holds.md b/.changeset/markdown-incremental-cache-holds.mdindex d92151d2e9..6f1189256e 100644--- a/.changeset/markdown-incremental-cache-holds.md+++ b/.changeset/markdown-incremental-cache-holds.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] Markdown streaming: `parseMarkdownIncremental` no longer throws away its settled blocks while a code fence is open, or when a chunk happens to end on a newline — both re-parsed the whole document, so a long streamed response got slower the longer it grew. Blocks rebuilt across a streamed 500-paragraph document: 126,756 → 1,869.+[fix] Markdown streaming: `parseMarkdownIncremental` no longer throws away its settled blocks while a code fence is open, or when a chunk happens to end on a newline — both re-parsed the whole document, so a long streamed response got slower the longer it grew. Blocks rebuilt across a streamed 500-paragraph document: 126,756 → 1,869 (#5407).@cixzhangdiff --git a/.changeset/markdown-source-ranges.md b/.changeset/markdown-source-ranges.mdindex bb70fb2fcb..0d53bd0431 100644--- a/.changeset/markdown-source-ranges.md+++ b/.changeset/markdown-source-ranges.md@@ -28,6 +28,6 @@ result gives the same node back.Blocks nested inside a list item or a blockquote carry no range: their childrenare parsed from text the parser reassembled with markers and `>` prefixes-removed, so an offset into it would not address the document.+removed, so an offset into it would not address the document (#5290).@lexsdiff --git a/.changeset/migrate-inline-merge-refs.md b/.changeset/migrate-inline-merge-refs.mdindex 9d360048fe..a12d7a67bb 100644--- a/.changeset/migrate-inline-merge-refs.md+++ b/.changeset/migrate-inline-merge-refs.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Migrate core components from inline mergeRefs calls to stable useMergedRefs callbacks.+[fix] Migrate core components from inline mergeRefs calls to stable useMergedRefs callbacks (#5267).@nynexman4464diff --git a/.changeset/multiselector-format-value.md b/.changeset/multiselector-format-value.mdindex c120a074f1..3b28fc5f0c 100644--- a/.changeset/multiselector-format-value.md+++ b/.changeset/multiselector-format-value.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[component] MultiSelector: rename the unreleased `formatTriggerCount` prop to `formatValue` and widen it to the whole trigger line. It now receives the selected items (`{value, label}[]`, count available as `.length`) and formats the trigger for `triggerDisplay="count"` and `"labels"`; `"badges"` renders elements, so it is not used there. `formatValue` matches NumberInput and Slider, so the same idea has one name across the system. Defaults are unchanged when the prop is absent.+[component] MultiSelector: rename the unreleased `formatTriggerCount` prop to `formatValue` and widen it to the whole trigger line. It now receives the selected items (`{value, label}[]`, count available as `.length`) and formats the trigger for `triggerDisplay="count"` and `"labels"`; `"badges"` renders elements, so it is not used there. `formatValue` matches NumberInput and Slider, so the same idea has one name across the system. Defaults are unchanged when the prop is absent (#5377).@Kevinjohndiff --git a/.changeset/powersearch-applies-operator-menu-limit.md b/.changeset/powersearch-applies-operator-menu-limit.mdindex 3322e251e2..f818d794c8 100644--- a/.changeset/powersearch-applies-operator-menu-limit.md+++ b/.changeset/powersearch-applies-operator-menu-limit.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] PowerSearch: `maxOperatorMenuItems` now caps suggestions in string, string-list, and entity-list value typeaheads, including values inside nested filters.+[fix] PowerSearch: `maxOperatorMenuItems` now caps suggestions in string, string-list, and entity-list value typeaheads, including values inside nested filters (#5242).@nynexman4464diff --git a/.changeset/powersearch-narrow-viewport-fit.md b/.changeset/powersearch-narrow-viewport-fit.mdindex 6c4d330b79..857e3064ad 100644--- a/.changeset/powersearch-narrow-viewport-fit.md+++ b/.changeset/powersearch-narrow-viewport-fit.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] PowerSearch: the edit popover now fits narrow viewports — its 400px minimum width yields to the screen width, and the filter row wraps instead of overflowing when long translated operator labels don't fit. An editor anchored near the screen edge now stays on its own side at the width available there, wrapping internally, instead of flipping across the anchor to keep 400px.+[fix] PowerSearch: the edit popover now fits narrow viewports — its 400px minimum width yields to the screen width, and the filter row wraps instead of overflowing when long translated operator labels don't fit. An editor anchored near the screen edge now stays on its own side at the width available there, wrapping internally, instead of flipping across the anchor to keep 400px (#4768).@AKnassadiff --git a/.changeset/promote-stepper-to-core.md b/.changeset/promote-stepper-to-core.mdindex d6f3ae8d96..5468e4eda2 100644--- a/.changeset/promote-stepper-to-core.md+++ b/.changeset/promote-stepper-to-core.md@@ -7,6 +7,6 @@Advancing one step now animates the connector. Every connector the four layouts draw — the separated bars and the on-track segments alike — grows its accent fill out of the segment's leading edge instead of swapping a background color, so moving forward reads as progress travelling the track. That one gesture is the only thing that animates: going back, jumping forward by more than one step, and mounting mid-flow all apply at once, as does any change under `prefers-reduced-motion`. Retreats are deliberately instant — run in reverse the same transition ends on a shrinking stub of accent, and a remnant still on the track reads as unfinished where the identical curve growing forward reads as arrived — and multi-step jumps are instant because a jump is a navigation rather than a progression, so sweeping a front across the crossed segments only makes the user sit out a journey they asked to skip. Where one span is drawn by several segments (the on-track layouts split a span between two steps, three when a content slot sits between them) the segments take abutting slices of the span's time and run linearly, so the fill reads as one line growing at a constant speed rather than pieces lighting in turn.-Five visual fixes land with the promotion. Horizontal steps now divide the track evenly instead of sizing to their own labels, so every progress segment is the same width regardless of how long a step is named. Number indicators shrink from 20px to 16px to match the check, ring, and custom-icon indicators, so a step swapping its number for a check as it completes no longer nudges the label beside it. A step description now occupies a 16px box rather than a 24px one — it previously inherited the page's line box instead of applying its own leading, which opened an 8px gap under the label. A step's content slot now starts flush with the label above it at every density: the slot renders outside the density-padded label area, so it was hanging one pad short of it. And a vertical on-track step carrying content keeps its connector unbroken — the content renders below the row that draws the line, so the track used to split open around any step with content.+Five visual fixes land with the promotion. Horizontal steps now divide the track evenly instead of sizing to their own labels, so every progress segment is the same width regardless of how long a step is named. Number indicators shrink from 20px to 16px to match the check, ring, and custom-icon indicators, so a step swapping its number for a check as it completes no longer nudges the label beside it. A step description now occupies a 16px box rather than a 24px one — it previously inherited the page's line box instead of applying its own leading, which opened an 8px gap under the label. A step's content slot now starts flush with the label above it at every density: the slot renders outside the density-padded label area, so it was hanging one pad short of it. And a vertical on-track step carrying content keeps its connector unbroken — the content renders below the row that draws the line, so the track used to split open around any step with content (#5201).@ernesttdiff --git a/.changeset/selector-divider-listbox-violation.md b/.changeset/selector-divider-listbox-violation.mdindex bb1172e2b6..614330a654 100644--- a/.changeset/selector-divider-listbox-violation.md+++ b/.changeset/selector-divider-listbox-violation.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] `Selector` and `MultiSelector` no longer expose their `{type: 'divider'}` separators to assistive technology. `role="listbox"` only permits `option`/`group` children, but the divider previously rendered `role="separator"` as a direct child of the listbox (axe `aria-required-children`, impact critical). The divider is decorative and carries no information the options don't, so it's now hidden from the accessibility tree via `aria-hidden`, matching the pattern already used for section headings.+[fix] `Selector` and `MultiSelector` no longer expose their `{type: 'divider'}` separators to assistive technology. `role="listbox"` only permits `option`/`group` children, but the divider previously rendered `role="separator"` as a direct child of the listbox (axe `aria-required-children`, impact critical). The divider is decorative and carries no information the options don't, so it's now hidden from the accessibility tree via `aria-hidden`, matching the pattern already used for section headings (#5107).@HelloOjasMutrejadiff --git a/.changeset/spinner-svg-ring.md b/.changeset/spinner-svg-ring.mdindex a4aa0d2f3c..680b8494f0 100644--- a/.changeset/spinner-svg-ring.md+++ b/.changeset/spinner-svg-ring.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[refactor] Spinner: the ring is drawn in SVG instead of `<canvas>`. The arc and track take their colours from the cascade (`currentColor` for `shade="inherit"`), so nothing resolves a colour in JS: a colour change after mount now repaints the ring instead of leaving it stale until it remounts, and mounting spinners no longer costs a `getComputedStyle` each. Rings are pinned to the document timeline's origin, so spinners mounted at different times turn in phase. No API, geometry or theme-target change.+[refactor] Spinner: the ring is drawn in SVG instead of `<canvas>`. The arc and track take their colours from the cascade (`currentColor` for `shade="inherit"`), so nothing resolves a colour in JS: a colour change after mount now repaints the ring instead of leaving it stale until it remounts, and mounting spinners no longer costs a `getComputedStyle` each. Rings are pinned to the document timeline's origin, so spinners mounted at different times turn in phase. No API, geometry or theme-target change (#5408).@cixzhangdiff --git a/.changeset/stabilize-hoisted-merged-refs.md b/.changeset/stabilize-hoisted-merged-refs.mdindex 6941e6ea65..e72436a40a 100644--- a/.changeset/stabilize-hoisted-merged-refs.md+++ b/.changeset/stabilize-hoisted-merged-refs.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Keep merged refs stable across Avatar, Button, SideNav, TabList, and TopNav.+[fix] Keep merged refs stable across Avatar, Button, SideNav, TabList, and TopNav (#5429).@nynexman4464diff --git a/.changeset/stable-text-refs.md b/.changeset/stable-text-refs.mdindex 70f39ed7cf..d0453f6aa2 100644--- a/.changeset/stable-text-refs.md+++ b/.changeset/stable-text-refs.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Add useMergedRefs and keep Text and Heading refs stable across rerenders.+[fix] Add useMergedRefs and keep Text and Heading refs stable across rerenders (#5266).@nynexman4464diff --git a/.changeset/structural-component-contract-docs-tjsk.md b/.changeset/structural-component-contract-docs-tjsk.mdindex 2153c231e8..11ae150d9f 100644--- a/.changeset/structural-component-contract-docs-tjsk.md+++ b/.changeset/structural-component-contract-docs-tjsk.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[docs] document missing props across structural components (CodeBlock, Toolbar) (#4163)+[docs] document missing props across structural components (CodeBlock, Toolbar) (#4317, part of #4163)@HelloOjasMutrejadiff --git a/.changeset/table-grouped-template-table-body.md b/.changeset/table-grouped-template-table-body.mdindex 412baf5094..5266c720a2 100644--- a/.changeset/table-grouped-template-table-body.md+++ b/.changeset/table-grouped-template-table-body.md@@ -14,6 +14,6 @@ table ends up with `<tr>` children and no `<tbody>` at all, and any CSS orquery aimed at `tbody` silently misses.The rows now sit in `<TableBody>`, the same element the data-driven `data={...}`-path renders, so styling, dividers, and column widths are unchanged.+path renders, so styling, dividers, and column widths are unchanged (#5278).@AKnassa @rubyycheungdiff --git a/.changeset/table-section-component-docs.md b/.changeset/table-section-component-docs.mdindex 1c1eea1bf8..1a36e3f460 100644--- a/.changeset/table-section-component-docs.md+++ b/.changeset/table-section-component-docs.md@@ -15,6 +15,6 @@ hydration.The three section components are now documented, listed on `Table`, and namedin the `children` prop description, in a best practice, and in `TableRow`'s-example.+example (#5278).@AKnassa @rubyycheungdiff --git a/.changeset/table-selection-row-highlight-opt-out.md b/.changeset/table-selection-row-highlight-opt-out.mdindex e364016440..bde7e63a73 100644--- a/.changeset/table-selection-row-highlight-opt-out.md+++ b/.changeset/table-selection-row-highlight-opt-out.md@@ -16,6 +16,6 @@ read.```tsxuseTableSelection({...config, hasRowHighlight: false});-```+``` (#5310)@ernesttdiff --git a/.changeset/tablist-aria-role.md b/.changeset/tablist-aria-role.mdindex 6369cbcab4..b4110172bc 100644--- a/.changeset/tablist-aria-role.md+++ b/.changeset/tablist-aria-role.md@@ -8,6 +8,6 @@**Nothing changes for a caller who passes no `role`**: the strip is the `<nav>` landmark with `aria-current` it has always been. Any other role still passes through to the element untouched.-Two development warnings come with the asserted role, and only with it. A tab with an `href` is a false statement inside a tablist, so the `href` is ignored and the warning says so. And a tab that controls nothing gets asked for a `panelId` — either that or an `aria-controls` you wrote yourself satisfies it, and a hand-written one is never overwritten. `aria-controls` is emitted only when you supply the id: pointing at a panel that does not exist is an invalid attribute value, which is worse than saying nothing. A menu or any other non-tab in a tablist strip is invalid markup, and warns too. The mirror case warns as well: a `panelId` on a strip that is not a tablist has no panel relationship to state, and is dropped.+Two development warnings come with the asserted role, and only with it. A tab with an `href` is a false statement inside a tablist, so the `href` is ignored and the warning says so. And a tab that controls nothing gets asked for a `panelId` — either that or an `aria-controls` you wrote yourself satisfies it, and a hand-written one is never overwritten. `aria-controls` is emitted only when you supply the id: pointing at a panel that does not exist is an invalid attribute value, which is worse than saying nothing. A menu or any other non-tab in a tablist strip is invalid markup, and warns too. The mirror case warns as well: a `panelId` on a strip that is not a tablist has no panel relationship to state, and is dropped (#5349).@cixzhangdiff --git a/.changeset/tablist-scroll-overflow.md b/.changeset/tablist-scroll-overflow.mdindex 1f7e0d63eb..47d39e2bbf 100644--- a/.changeset/tablist-scroll-overflow.md+++ b/.changeset/tablist-scroll-overflow.md@@ -4,6 +4,6 @@[feat] TabList: a strip narrower than its tabs now scrolls instead of spilling out of its container. Every tab stays a tab — nothing is hidden behind a menu — the edges fade to show there is more, and pointers that can hover get arrow affordances; keyboard and screen-reader users reach every tab with the arrow keys, which scrolls the focused tab into view. The selected tab is scrolled back into view whenever it would be out of sight, including on mount and when the host changes `value` itself. The new `overflow` prop takes `'auto'` (the default, which today always scrolls), `'scroll'`, or `'visible'` to keep the old spill-out layout. Built on the existing `useScrollOverflow` hook, so there is no new measurement machinery and no `Carousel` in the tab strip — the documented Carousel recipe, which announced every tab as "slide N of M", is no longer needed and the stories now use the built-in behaviour.-If you followed that recipe, nothing breaks: a `Carousel` still wrapping the tabs renders and behaves exactly as it did before, because its own scroll container absorbs the strip's, which then never overflows. Removing it is worth doing anyway — it drops the `region`/"slide N of M" wrapping from the accessibility tree, and the strip's own scrolling brings a tab that straddles the edge fully into view on focus, which the carousel does not.+If you followed that recipe, nothing breaks: a `Carousel` still wrapping the tabs renders and behaves exactly as it did before, because its own scroll container absorbs the strip's, which then never overflows. Removing it is worth doing anyway — it drops the `region`/"slide N of M" wrapping from the accessibility tree, and the strip's own scrolling brings a tab that straddles the edge fully into view on focus, which the carousel does not (#5348).@cixzhangdiff --git a/.changeset/theming-var-enumeration.md b/.changeset/theming-var-enumeration.mdindex 57c5b8e817..0a77b472db 100644--- a/.changeset/theming-var-enumeration.md+++ b/.changeset/theming-var-enumeration.md@@ -10,4 +10,4 @@ enumeration the theming surface is read from. Two guards ride on it: adocumented public var no component reads compiles to a declaration that neverapplies, and a var the component writes inline outranks every cascade layer, sono theme can reach it. Both had shipped; neither is visible in the generated-theme CSS the jsdom suites assert on.+theme CSS the jsdom suites assert on (#5409).diff --git a/.changeset/timeinput-parses-compact-am-pm-values-correctly-oqsg.md b/.changeset/timeinput-parses-compact-am-pm-values-correctly-oqsg.mdindex 6a5141d1e3..80fe893b76 100644--- a/.changeset/timeinput-parses-compact-am-pm-values-correctly-oqsg.md+++ b/.changeset/timeinput-parses-compact-am-pm-values-correctly-oqsg.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] TimeInput parses compact AM/PM values correctly+[fix] TimeInput parses compact AM/PM values correctly (#4026)@Kevinjohndiff --git a/.changeset/typeahead-tab-dismiss-on-keydown.md b/.changeset/typeahead-tab-dismiss-on-keydown.mdindex ed42ec5d28..0781d1bb29 100644--- a/.changeset/typeahead-tab-dismiss-on-keydown.md+++ b/.changeset/typeahead-tab-dismiss-on-keydown.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] Typeahead: Tab out of the field now moves focus to the next control. The result list is dismissed on the Tab keydown rather than from the blur that press produces — hiding a top-layer popover during the focusout makes Chrome abandon the in-flight focus move and drop focus to `<body>`, so the press appeared to do nothing. Selector and MultiSelector already dismissed on the keydown.+[fix] Typeahead: Tab out of the field now moves focus to the next control. The result list is dismissed on the Tab keydown rather than from the blur that press produces — hiding a top-layer popover during the focusout makes Chrome abandon the in-flight focus move and drop focus to `<body>`, so the press appeared to do nothing. Selector and MultiSelector already dismissed on the keydown (#5400).@cixzhang