An open source design system that's fully customizable and agent ready
TypeScript
docs: reference, credit and complete the v0.4.6 changesets
Cindy Zhang52851129c9e9
diff --git a/.changeset/avatargroup-audit-hardening.md b/.changeset/avatargroup-audit-hardening.mdindex faae0a468c..8eb67c0fe4 100644--- a/.changeset/avatargroup-audit-hardening.md+++ b/.changeset/avatargroup-audit-hardening.md@@ -2,7 +2,7 @@'@astryxdesign/core': patch----[fix] AvatarGroup: four defects out of the component audit, three of them in `AvatarGroupOverflow`.+[fix] AvatarGroup: four defects out of the component audit, three of them in `AvatarGroupOverflow` (#5055).The indicator was `display: flex` on a span, which is a block-level flex container, so the exported component rendered as a full-width bar instead of a circle anywhere outside an `AvatarGroup`: measured 1168px wide in a 1168px parent. It is `inline-flex` now; inside a group nothing changes, because a flex item is blockified either way.diff --git a/.changeset/blockquote-attribution-landmark.md b/.changeset/blockquote-attribution-landmark.mdindex 84202b4159..4d8eca7c65 100644--- a/.changeset/blockquote-attribution-landmark.md+++ b/.changeset/blockquote-attribution-landmark.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Blockquote: the `cite` attribution renders as a bare `<cite>` instead of being wrapped in a `<footer>`, which was becoming a `contentinfo` document landmark. Also guards the slot with `isRenderable`, so `cite={condition && author}` no longer emits an empty `<cite>`, and wraps long unbroken words instead of overflowing.+[fix] Blockquote: the `cite` attribution renders as a bare `<cite>` instead of being wrapped in a `<footer>`, which was becoming a `contentinfo` document landmark. Also guards the slot with `isRenderable`, so `cite={condition && author}` no longer emits an empty `<cite>`, and wraps long unbroken words instead of overflowing (#5144).@cixzhangdiff --git a/.changeset/bottom-sheet-floating-handle.md b/.changeset/bottom-sheet-floating-handle.mdindex aa87320edb..25e5aafa36 100644--- a/.changeset/bottom-sheet-floating-handle.md+++ b/.changeset/bottom-sheet-floating-handle.md@@ -2,7 +2,7 @@'@astryxdesign/core': patch----[fix] Bottom Sheet: float the grab handle so content sits closer to the top+[fix] Bottom Sheet: float the grab handle so content sits closer to the top (#5222)The drag area above the sheet's content was a 48px row in the sheet's flexcolumn, pushing everything below it down by its full height and reading as andiff --git a/.changeset/bottom-sheet-scrim-edge-hairline.md b/.changeset/bottom-sheet-scrim-edge-hairline.mdindex b04ab2b654..d1fbb78dbe 100644--- a/.changeset/bottom-sheet-scrim-edge-hairline.md+++ b/.changeset/bottom-sheet-scrim-edge-hairline.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] BottomSheet: give the sheet one uniform edge against the scrim. Two things were wrong in dark mode. The sheet drew no edge of its own — surface and scrim sit a few RGB steps apart and the `--shadow-high` drop shadow is black on near-black, so the left and right edges were invisible (measured 1.16:1 boundary contrast in dark against 2.89:1 in light); it now carries a `--border-width` / `--color-border` hairline on its three scrim-facing edges, the same treatment MobileNav gives its scrim-facing edge. And under a theme that packs an inset ring into `--shadow-high` (every bundled theme adds one in dark mode) that ring was painted over by an opaque content wrapper such as `Section`, so it showed only in the gap below where the content ended and the side edges appeared to change width partway down; the scrolling body now paints the surface across the sheet's whole inner box, hiding the ring evenly.+[fix] BottomSheet: give the sheet one uniform edge against the scrim. Two things were wrong in dark mode. The sheet drew no edge of its own — surface and scrim sit a few RGB steps apart and the `--shadow-high` drop shadow is black on near-black, so the left and right edges were invisible (measured 1.16:1 boundary contrast in dark against 2.89:1 in light); it now carries a `--border-width` / `--color-border` hairline on its three scrim-facing edges, the same treatment MobileNav gives its scrim-facing edge. And under a theme that packs an inset ring into `--shadow-high` (every bundled theme adds one in dark mode) that ring was painted over by an opaque content wrapper such as `Section`, so it showed only in the gap below where the content ended and the side edges appeared to change width partway down; the scrolling body now paints the surface across the sheet's whole inner box, hiding the ring evenly (#5305).@imdreamrunnerdiff --git a/.changeset/breadcrumbs-audit-20260822.md b/.changeset/breadcrumbs-audit-20260822.mdindex cee183ebb5..75ad034096 100644--- a/.changeset/breadcrumbs-audit-20260822.md+++ b/.changeset/breadcrumbs-audit-20260822.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Breadcrumbs: button crumbs keep the link's vertical padding, the variant reaches the item theme targets, and interactive crumbs paint the shared focus ring+[fix] Breadcrumbs: button crumbs keep the link's vertical padding, the variant reaches the item theme targets, and interactive crumbs paint the shared focus ring (#5332)@cixzhangdiff --git a/.changeset/cli-fix-integration-import-specifier.md b/.changeset/cli-fix-integration-import-specifier.mdindex 8e8efb2873..c62f03165b 100644--- a/.changeset/cli-fix-integration-import-specifier.md+++ b/.changeset/cli-fix-integration-import-specifier.md@@ -2,7 +2,7 @@'@astryxdesign/cli': patch----[fix] `component` built the import specifier for an integration component by joining the package name and the component name, which assumes every component is exported from a subpath named after itself. Components are commonly grouped behind a single entry point named after the concept, so the suggested import pointed at a subpath the package does not export and did not resolve.+[fix] `component` built the import specifier for an integration component by joining the package name and the component name, which assumes every component is exported from a subpath named after itself. Components are commonly grouped behind a single entry point named after the concept, so the suggested import pointed at a subpath the package does not export and did not resolve (#4810).The specifier is now resolved against the owning package's `exports` map, keyed on the directory the component's doc file sits in, and falls back to the package root when that directory is not an exported subpath. A specifier a doc file states for itself is also no longer overwritten.diff --git a/.changeset/codemod-jsx-rename-whitespace.md b/.changeset/codemod-jsx-rename-whitespace.mdindex 3d31ba8946..b042214321 100644--- a/.changeset/codemod-jsx-rename-whitespace.md+++ b/.changeset/codemod-jsx-rename-whitespace.md@@ -2,6 +2,6 @@'@astryxdesign/cli': patch----[fix] The upgrade codemod no longer collapses significant JSX whitespace when it renames an element tag. Renaming `<OldName>` next to text and a `{expression}` (e.g. `hello {name} world`) previously dropped the adjacent space (`hello {name}world`); element-tag renames are now spliced into the output so the surrounding JSX is left untouched.+[fix] The upgrade codemod no longer collapses significant JSX whitespace when it renames an element tag. Renaming `<OldName>` next to text and a `{expression}` (e.g. `hello {name} world`) previously dropped the adjacent space (`hello {name}world`); element-tag renames are now spliced into the output so the surrounding JSX is left untouched (#5149).@ejhammonddiff --git a/.changeset/codemod-xds-prefix-alias-collision.md b/.changeset/codemod-xds-prefix-alias-collision.mdnew file mode 100644index 0000000000..5697189302--- /dev/null+++ b/.changeset/codemod-xds-prefix-alias-collision.md@@ -0,0 +1,7 @@+---+'@astryxdesign/cli': patch+---++[fix] The XDS-prefix codemod no longer produces a file that will not compile. Dropping the prefix renames `XDSButton` to `Button`, but if the file already had a local binding called `Button` the rewrite collided with it and shadowed one of the two. The import is now aliased instead, so both survive and the file still typechecks (#5225).++@ejhammonddiff --git a/.changeset/dashboard-page-templates.md b/.changeset/dashboard-page-templates.mdnew file mode 100644index 0000000000..72ee22d347--- /dev/null+++ b/.changeset/dashboard-page-templates.md@@ -0,0 +1,7 @@+---+'@astryxdesign/cli': patch+---++[feat] Five dashboard page templates: `dashboard-cohort-funnel`, `dashboard-data`, `dashboard-executive-summary`, `dashboard-project-status` and `dashboard-service-monitoring`. Each is a complete page — layout, realistic sample data, and the component choices that go with the shape of the data — so `astryx template <name>` gives you something to edit rather than a blank frame (#5245).++@kentonquatmandiff --git a/.changeset/date-input-touch-snap-correction.md b/.changeset/date-input-touch-snap-correction.mdindex fcf6d5248d..f65c29e270 100644--- a/.changeset/date-input-touch-snap-correction.md+++ b/.changeset/date-input-touch-snap-correction.md@@ -2,7 +2,7 @@'@astryxdesign/core': patch----[fix] DateInput's touch calendar no longer rests between two months+[fix] DateInput's touch calendar no longer rests between two months (#5319)Swiping the month calendar on iOS could leave it parked a couple of columnsinto a pane: the left of March and the right of April on screen at once, underdiff --git a/.changeset/date-input-touch-surface.md b/.changeset/date-input-touch-surface.mdindex 32f315ddd0..d96c1d7477 100644--- a/.changeset/date-input-touch-surface.md+++ b/.changeset/date-input-touch-surface.md@@ -3,7 +3,7 @@---[feat] DateInput fits the pointer: a touch picker on a finger, the text field-on a mouse+on a mouse (#5243)`DateInput` has always been a control for a mouse — a field you type into witha calendar in a popover beside it. On a phone or a tablet that is the wrongdiff --git a/.changeset/disabled-cursor-guarantee.md b/.changeset/disabled-cursor-guarantee.mdindex d353189e79..5aa4fe7ca8 100644--- a/.changeset/disabled-cursor-guarantee.md+++ b/.changeset/disabled-cursor-guarantee.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] A disabled element answers the pointer with `default`, never an interactive cursor. Every `cursor` in core and lab carries `':is(:disabled,[aria-disabled="true"])': 'default'`, and the reset gives the same cursor to any disabled element that declares none — `[aria-disabled]` included, which previously got nothing. A lint rule and a Chromium sweep over every story keep it that way. Disabled elements sealed behind `pointer-events: none` are unchanged: the pointer never reaches them, so their cursor comes from an ancestor — which is why the guarantee is `default` rather than a distinct disabled cursor the library could only paint on some of them.+[fix] A disabled element answers the pointer with `default`, never an interactive cursor. Every `cursor` in core and lab carries `':is(:disabled,[aria-disabled="true"])': 'default'`, and the reset gives the same cursor to any disabled element that declares none — `[aria-disabled]` included, which previously got nothing. A lint rule and a Chromium sweep over every story keep it that way. Disabled elements sealed behind `pointer-events: none` are unchanged: the pointer never reaches them, so their cursor comes from an ancestor — which is why the guarantee is `default` rather than a distinct disabled cursor the library could only paint on some of them (#5323).@cixzhangdiff --git a/.changeset/disabled-no-hover-state.md b/.changeset/disabled-no-hover-state.mdindex 1493ed5e82..a837d64b41 100644--- a/.changeset/disabled-no-hover-state.md+++ b/.changeset/disabled-no-hover-state.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Disabled elements no longer paint a hover state: every self-`:hover` in core and lab, and every `:hover` a theme authors, now carries the zero-specificity guard `:hover:where(:not(:disabled,[aria-disabled="true"]))`, so existing overrides weigh exactly what they weighed before. A lint rule and a Chromium sweep over every story keep it that way.+[fix] Disabled elements no longer paint a hover state: every self-`:hover` in core and lab, and every `:hover` a theme authors, now carries the zero-specificity guard `:hover:where(:not(:disabled,[aria-disabled="true"]))`, so existing overrides weigh exactly what they weighed before. A lint rule and a Chromium sweep over every story keep it that way (#5247).@cixzhangdiff --git a/.changeset/input-clear-button-touch-hit-area.md b/.changeset/input-clear-button-touch-hit-area.mdindex b2c52d1b57..7397ebb24f 100644--- a/.changeset/input-clear-button-touch-hit-area.md+++ b/.changeset/input-clear-button-touch-hit-area.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] InputClearButton: the clear (✕) affordance now meets the WCAG 2.5.8 AA 24×24 minimum on touch. The shared button rendered a 20px glyph with a 20px tap target, so every input that clears through it — Typeahead, Tokenizer, FileInput and the rest of the family — was under the floor on a phone. An `::after` overlay now expands the tappable region to 24×24, gated behind `@media (pointer: coarse)`: on a fine pointer the overlay is not generated at all, because a mouse is precise enough, an unconditional overlay could overlap neighboring controls in dense desktop layouts, and an overlay covering the button would take hover away from the `astryx-input-clear-icon` theme target. The visual glyph is unchanged at every breakpoint, and the overlay stops at 24px so it stays clear of the 8px adornment gap and the input's own caret area.+[fix] InputClearButton: the clear (✕) affordance now meets the WCAG 2.5.8 AA 24×24 minimum on touch. The shared button rendered a 20px glyph with a 20px tap target, so every input that clears through it — Typeahead, Tokenizer, FileInput and the rest of the family — was under the floor on a phone. An `::after` overlay now expands the tappable region to 24×24, gated behind `@media (pointer: coarse)`: on a fine pointer the overlay is not generated at all, because a mouse is precise enough, an unconditional overlay could overlap neighboring controls in dense desktop layouts, and an overlay covering the button would take hover away from the `astryx-input-clear-icon` theme target. The visual glyph is unchanged at every breakpoint, and the overlay stops at 24px so it stays clear of the 8px adornment gap and the input's own caret area (#4956).@rubyycheungdiff --git a/.changeset/mobile-nav-entry-animation.md b/.changeset/mobile-nav-entry-animation.mdindex f7e119dcd8..551feb04ab 100644--- a/.changeset/mobile-nav-entry-animation.md+++ b/.changeset/mobile-nav-entry-animation.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] MobileNav: the drawer now slides in when it opens, instead of only sliding out when it closes. Two things were needed, and each is useless without the other. First, the dialog is `display: none` while closed, so the drawer's first rendered frame already holds the on-screen transform and a transition has no before-change value to run from — `@starting-style` supplies it, for the drawer's transform and for the `::backdrop`'s opacity. Second, the dialog clipped the off-screen drawer with `overflow: hidden`, which makes it a scroll container; a scroll container in the top layer whose subtree holds another scroller (the drawer's content area) does not paint a `@starting-style` entry transition for its descendants in Chromium — the transition ticks in the CSSOM while every painted frame shows the end value. `overflow: clip` clips identically without creating a scroll container. The drawer now slides in from its own edge (mirrored under RTL) and the scrim fades up, both on `--duration-medium` and both collapsing under `prefers-reduced-motion`, exactly as the close already did.+[fix] MobileNav: the drawer now slides in when it opens, instead of only sliding out when it closes. Two things were needed, and each is useless without the other. First, the dialog is `display: none` while closed, so the drawer's first rendered frame already holds the on-screen transform and a transition has no before-change value to run from — `@starting-style` supplies it, for the drawer's transform and for the `::backdrop`'s opacity. Second, the dialog clipped the off-screen drawer with `overflow: hidden`, which makes it a scroll container; a scroll container in the top layer whose subtree holds another scroller (the drawer's content area) does not paint a `@starting-style` entry transition for its descendants in Chromium — the transition ticks in the CSSOM while every painted frame shows the end value. `overflow: clip` clips identically without creating a scroll container. The drawer now slides in from its own edge (mirrored under RTL) and the scrim fades up, both on `--duration-medium` and both collapsing under `prefers-reduced-motion`, exactly as the close already did (#5218).@imdreamrunnerdiff --git a/.changeset/number-input-stepper-padding-var.md b/.changeset/number-input-stepper-padding-var.mdindex dac844124c..fbcd2eb9e8 100644--- a/.changeset/number-input-stepper-padding-var.md+++ b/.changeset/number-input-stepper-padding-var.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] NumberInput: the number-stepper column now tracks a themed padding and radius instead of assuming the defaults. Theming `number-input` padding left the steppers short of the field edges (a gap top and bottom), and a themed `borderRadius` rounded the field while the stepper corners kept the default radius. The wrapper's padding now goes through the shared container expansion, so it is picked up from any spelling a theme writes it in — `padding: 14px 20px`, `paddingBlock`, or a single `paddingBlockStart` — and both the wrapper and the column read the resulting per-side `--astryx-number-input-padding-*` tokens; an asymmetric `paddingBlock: 4px 12px` is cancelled correctly at each edge. A themed `number-input` borderRadius now also reaches `--_field-radius`, which the column's outer corners follow. Byte-identical by default, and inert for the no-stepper case and every other input.+[fix] NumberInput: the number-stepper column now tracks a themed padding and radius instead of assuming the defaults. Theming `number-input` padding left the steppers short of the field edges (a gap top and bottom), and a themed `borderRadius` rounded the field while the stepper corners kept the default radius. The wrapper's padding now goes through the shared container expansion, so it is picked up from any spelling a theme writes it in — `padding: 14px 20px`, `paddingBlock`, or a single `paddingBlockStart` — and both the wrapper and the column read the resulting per-side `--astryx-number-input-padding-*` tokens; an asymmetric `paddingBlock: 4px 12px` is cancelled correctly at each edge. A themed `number-input` borderRadius now also reaches `--_field-radius`, which the column's outer corners follow. Byte-identical by default, and inert for the no-stepper case and every other input (#5181).@freddymetadiff --git a/.changeset/overlay-padding-var-isolation.md b/.changeset/overlay-padding-var-isolation.mdindex 40e54dcdc4..493f79341d 100644--- a/.changeset/overlay-padding-var-isolation.md+++ b/.changeset/overlay-padding-var-isolation.md@@ -2,7 +2,7 @@'@astryxdesign/core': patch----[fix] Stop the container padding system at every overlay boundary. Follow-up to #5209, which zeroed `--container-padding-*` on four overlay roots and closed the visible overflow in #5208.+[fix] Stop the container padding system at every overlay boundary. Follow-up to #5209, which zeroed `--container-padding-*` on four overlay roots and closed the visible overflow in #5208 (#5231).Two gaps remained. The variables descendants ADD (`--layout-padding-*`, and a Section's propagated padding) still crossed the boundary, so an unpadded `Section` inside an overlay took the page's padding instead of the theme default — 40px where 16px was meant. And `Lightbox`, `ContextMenu` and `HoverCard` were never covered.diff --git a/.changeset/physical-block-padding-container-expansion.md b/.changeset/physical-block-padding-container-expansion.mdindex d9caa1bced..edd2264028 100644--- a/.changeset/physical-block-padding-container-expansion.md+++ b/.changeset/physical-block-padding-container-expansion.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Theming: a physical `paddingTop`/`paddingBottom` now reaches the container padding expansion, so `card`, `dialog`, `section` and `number-input` track it the way they already track the logical spellings. A physical block longhand matched none of the padding property names the expansion recognizes, so it landed raw on the element while the component's internals kept reading the default — the NumberInput stepper column came up ~10px short of the field edges, and container bleed compensated by the wrong amount. Mixing spellings was worse than either alone: `padding: '10px'` plus `paddingTop: '14px'` published 10px in the tokens while the element painted 14px on top. `padding-top` and `padding-bottom` ARE the block edges in every horizontal writing mode, so this normalization assumes no direction. `paddingLeft`/`paddingRight` are deliberately unchanged: they are direction-relative — left is inline-start in LTR and inline-end in RTL — and the tokens are consumed by logical properties, so routing them would silently move the padding to the opposite edge under RTL. They keep their physical meaning, exactly as before.+[fix] Theming: a physical `paddingTop`/`paddingBottom` now reaches the container padding expansion, so `card`, `dialog`, `section` and `number-input` track it the way they already track the logical spellings. A physical block longhand matched none of the padding property names the expansion recognizes, so it landed raw on the element while the component's internals kept reading the default — the NumberInput stepper column came up ~10px short of the field edges, and container bleed compensated by the wrong amount. Mixing spellings was worse than either alone: `padding: '10px'` plus `paddingTop: '14px'` published 10px in the tokens while the element painted 14px on top. `padding-top` and `padding-bottom` ARE the block edges in every horizontal writing mode, so this normalization assumes no direction. `paddingLeft`/`paddingRight` are deliberately unchanged: they are direction-relative — left is inline-start in LTR and inline-end in RTL — and the tokens are consumed by logical properties, so routing them would silently move the padding to the opposite edge under RTL. They keep their physical meaning, exactly as before (#5244).@cixzhangdiff --git a/.changeset/plaindate-locale-formatting.md b/.changeset/plaindate-locale-formatting.mdindex 91a46009a5..2617036510 100644--- a/.changeset/plaindate-locale-formatting.md+++ b/.changeset/plaindate-locale-formatting.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] `DateInput`, `DateTimeInput`, `DateRangeInput`, and `Calendar` now format and parse dates using the ambient `InternationalizationProvider` locale instead of the host/browser locale. `plainDateFormat` (backing `formatSharedDate`) previously called `Intl.DateTimeFormat(undefined, ...)`, and `dateParser`'s day/month disambiguation heuristic for ambiguous numeric input (e.g. `3/4/2026`) called `Intl.DateTimeFormat()` with no locale at all, so a tree wrapped in a non-English `locale` still formatted and parsed dates using the host locale.+[fix] `DateInput`, `DateTimeInput`, `DateRangeInput`, and `Calendar` now format and parse dates using the ambient `InternationalizationProvider` locale instead of the host/browser locale. `plainDateFormat` (backing `formatSharedDate`) previously called `Intl.DateTimeFormat(undefined, ...)`, and `dateParser`'s day/month disambiguation heuristic for ambiguous numeric input (e.g. `3/4/2026`) called `Intl.DateTimeFormat()` with no locale at all, so a tree wrapped in a non-English `locale` still formatted and parsed dates using the host locale (#5120).@HelloOjasMutrejadiff --git a/.changeset/provider-backed-locale-hooks.md b/.changeset/provider-backed-locale-hooks.mdindex 9edc0d6bb1..640d315634 100644--- a/.changeset/provider-backed-locale-hooks.md+++ b/.changeset/provider-backed-locale-hooks.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[feat] Export `useLocale` and `useCollator` for provider-backed formatting and comparison+[feat] Export `useLocale` and `useCollator` for provider-backed formatting and comparison (#5194)@nynexman4464diff --git a/.changeset/provider-locale-migrations.md b/.changeset/provider-locale-migrations.mdindex cfcc094b99..ff9b34ad85 100644--- a/.changeset/provider-locale-migrations.md+++ b/.changeset/provider-locale-migrations.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] Use the InternationalizationProvider locale for sorting, formatting, and speech defaults+[fix] Use the InternationalizationProvider locale for sorting, formatting, and speech defaults (#5195)@nynexman4464diff --git a/.changeset/radio-list-item-click-target.md b/.changeset/radio-list-item-click-target.mdindex 253b88594b..eb9d64110a 100644--- a/.changeset/radio-list-item-click-target.md+++ b/.changeset/radio-list-item-click-target.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] RadioListItem: the whole row is now a click target. Clicking the description — or the empty space in a row's hover area — selects the radio, matching CheckboxListItem. Previously only the radio and its label text responded, so the description and surrounding row were dead space. The row delegates surface clicks to the radio input (one tab stop per option preserved), and the radio keeps its accessible name via `aria-label`.+[fix] RadioListItem: the whole row is now a click target. Clicking the description — or the empty space in a row's hover area — selects the radio, matching CheckboxListItem. Previously only the radio and its label text responded, so the description and surrounding row were dead space. The row delegates surface clicks to the radio input (one tab stop per option preserved), and the radio keeps its accessible name via `aria-label` (#5143).@freddymetadiff --git a/.changeset/radio-list-item-row-state-variants.md b/.changeset/radio-list-item-row-state-variants.mdindex 13c02f1182..8e268f167e 100644--- a/.changeset/radio-list-item-row-state-variants.md+++ b/.changeset/radio-list-item-row-state-variants.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[feat] RadioListItem: the `radio-list-item` row theme target now carries `size`, `selected`, and `disabled` state variants (matching `multi-selector-option`), so themes can style selected or disabled rows.+[feat] RadioListItem: the `radio-list-item` row theme target now carries `size`, `selected`, and `disabled` state variants (matching `multi-selector-option`), so themes can style selected or disabled rows (#5143).@freddymetadiff --git a/.changeset/radio-list-item-themeable-row-surface.md b/.changeset/radio-list-item-themeable-row-surface.mdindex 0bb6b919a8..3199ad8aca 100644--- a/.changeset/radio-list-item-themeable-row-surface.md+++ b/.changeset/radio-list-item-themeable-row-surface.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[feat] RadioListItem: the `radio-list-item` theme target now rides the painting row element (converging with `list-item`), so a theme can style the row's hover background, padding, and border radius — previously it sat on a layout-only wrapper that painted nothing. The default (unthemed) row appearance is unchanged: it stays a bare surface with no row padding, radius, or hover/selected background (only the radio indicator tints on hover).+[feat] RadioListItem: the `radio-list-item` theme target now rides the painting row element (converging with `list-item`), so a theme can style the row's hover background, padding, and border radius — previously it sat on a layout-only wrapper that painted nothing. The default (unthemed) row appearance is unchanged: it stays a bare surface with no row padding, radius, or hover/selected background (only the radio indicator tints on hover) (#5143).@freddymetadiff --git a/.changeset/reset-overlay-container-padding.md b/.changeset/reset-overlay-container-padding.mdindex 5fcfa36205..f72bdbb258 100644--- a/.changeset/reset-overlay-container-padding.md+++ b/.changeset/reset-overlay-container-padding.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Reset container padding custom properties on overlay elements (`BottomSheet`, `Dialog`, `MobileNav`, `Popover`) to prevent nested `Section` components from inheriting ancestor section padding.+[fix] Reset container padding custom properties on overlay elements (`BottomSheet`, `Dialog`, `MobileNav`, `Popover`) to prevent nested `Section` components from inheriting ancestor section padding (#5209).@Geervandiff --git a/.changeset/resize-handle-grab-zone-cross-axis.md b/.changeset/resize-handle-grab-zone-cross-axis.mdindex 769cf86a4c..a5462314ab 100644--- a/.changeset/resize-handle-grab-zone-cross-axis.md+++ b/.changeset/resize-handle-grab-zone-cross-axis.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] ResizeHandle: dragging the lower half of a tall handle works again. The invisible grab zone is stretched along the handle, but the offset that biases it onto the pill also carried the pill's own `-50%` centering shift — so the zone slid half the handle's length off the divider. On a full-height panel at 1440x900 the 16x900 hit box sat at y=-434, leaving everything below the pill's centre dead: a pointerdown on the visible grip's centre, or anywhere lower, started no drag at all. The dead region grew with the panel, and the same shift stranded the grab zone sideways on vertical handles. The bias now moves the zone along the pill's axis only.+[fix] ResizeHandle: dragging the lower half of a tall handle works again. The invisible grab zone is stretched along the handle, but the offset that biases it onto the pill also carried the pill's own `-50%` centering shift — so the zone slid half the handle's length off the divider. On a full-height panel at 1440x900 the 16x900 hit box sat at y=-434, leaving everything below the pill's centre dead: a pointerdown on the visible grip's centre, or anywhere lower, started no drag at all. The dead region grew with the panel, and the same shift stranded the grab zone sideways on vertical handles. The bias now moves the zone along the pill's axis only (#5198).@cixzhangdiff --git a/.changeset/scroll-lock-scrollbar-gutter.md b/.changeset/scroll-lock-scrollbar-gutter.mdindex a11bf97b4e..076d723c4b 100644--- a/.changeset/scroll-lock-scrollbar-gutter.md+++ b/.changeset/scroll-lock-scrollbar-gutter.md@@ -2,7 +2,7 @@'@astryxdesign/core': patch----[fix] Opening a Dialog, BottomSheet, Lightbox, or MobileNav no longer shifts the page sideways when the browser has a classic scrollbar+[fix] Opening a Dialog, BottomSheet, Lightbox, or MobileNav no longer shifts the page sideways when the browser has a classic scrollbar (#5219)@imdreamrunnerdiff --git a/.changeset/section-stack-center-block-edge-padding.md b/.changeset/section-stack-center-block-edge-padding.mdindex 8a8a787ff7..f607a2c3c2 100644--- a/.changeset/section-stack-center-block-edge-padding.md+++ b/.changeset/section-stack-center-block-edge-padding.md@@ -2,7 +2,7 @@'@astryxdesign/core': patch----[feat] `Section`, `Stack` (with `HStack` / `VStack`) and `Center` accept a padding prop for each of the four edges — `paddingBlockStart`, `paddingBlockEnd`, `paddingInlineStart` and `paddingInlineEnd` — so an edge can take its own spacing step without an `xstyle` escape hatch. `Section` also gains the `paddingInline` axis prop it was missing, so all three components now expose the same seven-prop set.+[feat] `Section`, `Stack` (with `HStack` / `VStack`) and `Center` accept a padding prop for each of the four edges — `paddingBlockStart`, `paddingBlockEnd`, `paddingInlineStart` and `paddingInlineEnd` — so an edge can take its own spacing step without an `xstyle` escape hatch. `Section` also gains the `paddingInline` axis prop it was missing, so all three components now expose the same seven-prop set (#5224).Each prop takes the same spacing scale as `padding`, and resolution is most-specific-wins, per edge:diff --git a/.changeset/segmented-control-single-line-label.md b/.changeset/segmented-control-single-line-label.mdindex bc7450c934..7e0abcb811 100644--- a/.changeset/segmented-control-single-line-label.md+++ b/.changeset/segmented-control-single-line-label.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] SegmentedControl: keep item labels on a single line, truncating overflow with an ellipsis instead of wrapping to multiple lines+[fix] SegmentedControl: keep item labels on a single line, truncating overflow with an ellipsis instead of wrapping to multiple lines (#5035)@ernesttdiff --git a/.changeset/selector-option-description-trigger-value.md b/.changeset/selector-option-description-trigger-value.mdindex 3f92240b46..8404839dc8 100644--- a/.changeset/selector-option-description-trigger-value.md+++ b/.changeset/selector-option-description-trigger-value.md@@ -2,7 +2,7 @@'@astryxdesign/core': patch----[fix] Selector: `SelectorOptionData` gains `description`, and the closed trigger now shows the selected option instead of just its label. The two-line option row `SelectorOption` draws was unreachable from the `options` prop — the data type carried only `value/label/disabled/icon` — so consumers kept a side map of descriptions keyed by value and re-rendered the row through `renderOption`. `description` now sits on the option data and `DefaultOption` forwards it. On the trigger, the selected option's own `icon` renders in the closed state (`startIcon` still wins when set, so a pinned field icon never doubles up), which retires the app-side `startIcon={value === 'x' ? … : …}` mirroring of state the component already knows. `renderValue` is the seam for drawing the selection yourself — the description included.+[fix] Selector: `SelectorOptionData` gains `description`, and the closed trigger now shows the selected option instead of just its label. The two-line option row `SelectorOption` draws was unreachable from the `options` prop — the data type carried only `value/label/disabled/icon` — so consumers kept a side map of descriptions keyed by value and re-rendered the row through `renderOption`. `description` now sits on the option data and `DefaultOption` forwards it. On the trigger, the selected option's own `icon` renders in the closed state (`startIcon` still wins when set, so a pinned field icon never doubles up), which retires the app-side `startIcon={value === 'x' ? … : …}` mirroring of state the component already knows. `renderValue` is the seam for drawing the selection yourself — the description included (#5202).[feat] Item: new `layout` prop — `'stacked'` (default, unchanged) or `'inline'`, which keeps the description on the label's line with the description ellipsizing first. The inline row centers its two lines rather than sharing a baseline: two font sizes on one baseline make a line box taller than either line, which would push a fixed-height host off its size token. Every row built on `Item` gets the axis, `SelectorOption` included.diff --git a/.changeset/selector-option-row-theme-target.md b/.changeset/selector-option-row-theme-target.mdindex 3358257460..5c2be06da1 100644--- a/.changeset/selector-option-row-theme-target.md+++ b/.changeset/selector-option-row-theme-target.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[feat] Selector: add the `selector-option-row` theme target on the dropdown option row, carrying `size` plus `selected`/`disabled` state — so a theme can restyle row padding and density directly (mirroring `multi-selector-option`), instead of reaching the bare `role="option"` element with a structural selector.+[feat] Selector: add the `selector-option-row` theme target on the dropdown option row, carrying `size` plus `selected`/`disabled` state — so a theme can restyle row padding and density directly (mirroring `multi-selector-option`), instead of reaching the bare `role="option"` element with a structural selector (#5179).@freddymetadiff --git a/.changeset/slider-vertical-touch-target.md b/.changeset/slider-vertical-touch-target.mdindex 703ed548f4..ec3c58724b 100644--- a/.changeset/slider-vertical-touch-target.md+++ b/.changeset/slider-vertical-touch-target.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] `Slider` with `orientation="vertical"` now gets the same 24px touch hit area the horizontal one got: its track was still only 20px wide on coarse pointers, under the WCAG 2.5.8 AA minimum. The whole track is the tap target for both orientations — the fix that floored the horizontal track's block size did nothing for vertical, whose short axis is the inline one — so the inline size is now floored to 24px on touch, with the same `@media (pointer: coarse)` gate. The rail, fill, marks and thumb all center on the inline 50%, so nothing visible moves and desktop is untouched.+[fix] `Slider` with `orientation="vertical"` now gets the same 24px touch hit area the horizontal one got: its track was still only 20px wide on coarse pointers, under the WCAG 2.5.8 AA minimum. The whole track is the tap target for both orientations — the fix that floored the horizontal track's block size did nothing for vertical, whose short axis is the inline one — so the inline size is now floored to 24px on touch, with the same `@media (pointer: coarse)` gate. The rail, fill, marks and thumb all center on the inline 50%, so nothing visible moves and desktop is untouched (#5173).@imdreamrunnerdiff --git a/.changeset/syntax-theme-barrel-use-client.md b/.changeset/syntax-theme-barrel-use-client.mdindex f1ddc2f1e0..8d5f62dc7e 100644--- a/.changeset/syntax-theme-barrel-use-client.md+++ b/.changeset/syntax-theme-barrel-use-client.md@@ -2,7 +2,7 @@'@astryxdesign/core': patch----[fix] `@astryxdesign/core/theme/syntax` is importable from a server component again: the presets are data, not client references.+[fix] `@astryxdesign/core/theme/syntax` is importable from a server component again: the presets are data, not client references (#5076).The subpath's barrel carried `'use client'`, and it is the only entry point for the syntax module. React therefore replaced *every* export with a client reference for a server importer — including `dracula`, `oneLight`, `allSyntaxPresets`, `syntaxTokenDefaults` and `defineSyntaxTheme`, none of which need a boundary. Reading a preset in a Next.js server module (deriving a code-block ground, emitting theme CSS at build time) got a proxy instead of data, so `preset.tokens` was `undefined` and the failure surfaced far from its cause — the same import under plain Node worked perfectly.diff --git a/.changeset/toast-contrast-aware-media-theme.md b/.changeset/toast-contrast-aware-media-theme.mdindex 20f891230e..dfed21c8ee 100644--- a/.changeset/toast-contrast-aware-media-theme.md+++ b/.changeset/toast-contrast-aware-media-theme.md@@ -2,7 +2,7 @@'@astryxdesign/core': patch----[feat] MediaTheme: add `mode="auto"` and `mode="off"`+[feat] MediaTheme: add `mode="auto"` and `mode="off"` (#5299)A theme is free to define `--color-background-inverted` as something that isnot inverted — and a component that hardcodes `mode="dark"` then paints whitediff --git a/.changeset/tooltip-and-hovercard-tap-to-open-where-there-is-tzru.md b/.changeset/tooltip-and-hovercard-tap-to-open-where-there-is-tzru.mdindex 556cbb3bec..c2d6647b1b 100644--- a/.changeset/tooltip-and-hovercard-tap-to-open-where-there-is-tzru.md+++ b/.changeset/tooltip-and-hovercard-tap-to-open-where-there-is-tzru.md@@ -2,7 +2,7 @@'@astryxdesign/core': patch----[feat] Tooltip and HoverCard: tap to open where there is no hover+[feat] Tooltip and HoverCard: tap to open where there is no hover (#5248)Hover is the one trigger a touch screen cannot express, and both componentswere answering that badly. `Tooltip` suppressed itself on any device reporting@@ -38,4 +38,4 @@ button, so the `auto` rule would hand the tap to the control — but revealingthe tooltip is that button's only purpose, and suppressing it left anInfoTip's content unreachable on a phone.-@rubycheung+@rubyycheung