Skip to content

An open source design system that's fully customizable and agent ready

TypeScript

chore(changesets): link v0.7.5 final-state evidence (#8544)

Cindy Zhangd055fb7d030a
diff --git a/.changeset/announce-same-frame-join.md b/.changeset/announce-same-frame-join.md
index e8af16beed..58f7dc3fd0 100644
--- a/.changeset/announce-same-frame-join.md
+++ b/.changeset/announce-same-frame-join.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] useAnnounce: messages announced in the same frame are now joined, in order, into one announcement instead of the last one replacing the others, and an identical repeat is spoken once, so a screen reader no longer misses an earlier status such as a result count announced alongside a confirmation. An empty message still clears the region, including joined messages not yet spoken. This meets the shared-channel requirement in spec:AST-086 (FR9).
+[fix] useAnnounce: messages announced in the same frame are now joined, in order, into one announcement instead of the last one replacing the others, and an identical repeat is spoken once, so a screen reader no longer misses an earlier status such as a result count announced alongside a confirmation. An empty message still clears the region, including joined messages not yet spoken. This meets the shared-channel requirement in spec:AST-086 (FR9). Introduced in [#8244](https://github.com/facebook/astryx/pull/8244); final-state evidence: [#8294](https://github.com/facebook/astryx/pull/8294).
@cixzhang
diff --git a/.changeset/slider-one-pointer-per-drag.md b/.changeset/slider-one-pointer-per-drag.md
index efec21482e..797a6460bf 100644
--- a/.changeset/slider-one-pointer-per-drag.md
+++ b/.changeset/slider-one-pointer-per-drag.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Slider: a drag belongs to the pointer that started it. A second finger that lands on the slider, moves or lifts during a drag no longer moves the value, takes over the drag or ends it, and two fingers can still drag two sliders at once. A drag whose pointer capture is lost without a pointer up also ends, with one `onChangeEnd`, so the slider keeps answering new presses.
+[fix] Slider: a drag belongs to the pointer that started it. A second finger that lands on the slider, moves or lifts during a drag no longer moves the value, takes over the drag or ends it, and two fingers can still drag two sliders at once. A drag whose pointer capture is lost without a pointer up also ends, with one `onChangeEnd`, so the slider keeps answering new presses. Introduced in [#8152](https://github.com/facebook/astryx/pull/8152); final-state evidence: [#8284](https://github.com/facebook/astryx/pull/8284).
@vjeux
diff --git a/.changeset/status-color-roles.md b/.changeset/status-color-roles.md
index bfcc260571..07b29898f2 100644
--- a/.changeset/status-color-roles.md
+++ b/.changeset/status-color-roles.md
@@ -11,11 +11,12 @@
'@astryxdesign/theme-y2k': patch
---
-[feat] Status colours now have a role for each surface, and Info is a new status. For each of info, success, warning, and error: `--color-<status>` is the strong fill and `--color-on-<status>` is content on it, at 4.5:1 or more; `--color-<status>-muted` is the pale fill, with `--color-on-<status>-muted` content; and `--color-text-<status>` is readable status text on the page and cards, with `--color-icon-<status>` and `--color-border-<status>` (status icons and borders) defaulting to it. `--color-info`, `--color-on-info`, `--color-info-muted`, and the other Info roles are new and independent of the accent. Tailwind gains `bg-info`, `bg-info-muted`, `text-on-<status>`, `text-on-<status>-muted`, and `text-status-<status>` (the status text role).
+[feat] Status colours now have a role for each surface, and Info is a new status. For each of info, success, warning, and error: `--color-<status>` is the strong fill and `--color-on-<status>` is content on it, at 4.5:1 or more; `--color-<status>-muted` is the pale fill, with `--color-on-<status>-muted` content; and `--color-text-<status>` is readable status text on the page and cards, with `--color-icon-<status>` and `--color-border-<status>` (status icons and borders) defaulting to it. `--color-info`, `--color-on-info`, `--color-info-muted`, and the other Info roles are new and independent of the accent. Tailwind gains `bg-info`, `bg-info-muted`, `text-on-<status>`, `text-on-<status>-muted`, and `text-status-<status>` (the status text role). Introduced in [#7657](https://github.com/facebook/astryx/pull/7657).
`--color-success`, `--color-warning`, and `--color-error` and `bg-<status>` keep their meaning as the strong fills. Tailwind now projects each status by paint property: `text-`, `decoration-`, `placeholder-`, and `caret-<status>` read the status text role, and `border-`, `divide-`, `outline-`, and `ring-<status>` read the status border role, so status text and lines are readable on the page; `bg-`, `accent-`, `fill-`, `stroke-<status>`, shadow colours, and gradients keep the strong fill. for example, Core's light `text-warning` is now `#753F07` instead of `#E9AF08`, and `text-success` is `#09441F` instead of `#0D8626`. To keep the fill colour on text, use `text-[var(--color-warning)]`.
What changes on screen:
+
- Core's dark Error content (`--color-on-error`) is now `#0A1317` instead of white, so text on dark-mode error fills reaches 4.5:1. Core's Info Badge uses `--color-info` (`#0064E0`) instead of the accent; in dark mode the accent was `#2694FE`.
- Icon `color="info|success|warning|error"`, Stepper status glyphs, and Chat tool-call status icons use the icon roles, which are the readable text colours. For example, Core's success icon is now `#09441F` (light) instead of `#0D8626`.
- Input and FileInput status borders use the border roles. Core's light warning border is now `#753F07` instead of `#E9AF08`. Butter's light success and warning input rims are now mid-ramp stops that reach 3:1.
diff --git a/.changeset/typeahead-edit-focus-in-tap.md b/.changeset/typeahead-edit-focus-in-tap.md
index 009f0567bd..709cdc68d3 100644
--- a/.changeset/typeahead-edit-focus-in-tap.md
+++ b/.changeset/typeahead-edit-focus-in-tap.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Taps that start typing in a search field raise the touch keyboard. A tap on a Typeahead's selected value (edit mode) and a tap on the clear button of a Selector or MultiSelector search row now focus the input inside the tap itself instead of one frame later; iOS raises its keyboard only for a focus made while the browser is still handling the tap, so the deferred focus left a caret with no keyboard until a second tap. A clear tapped while the keyboard is already up keeps it up, as before.
+[fix] Taps that start typing in a search field raise the touch keyboard. A tap on a Typeahead's selected value (edit mode) and a tap on the clear button of a Selector or MultiSelector search row now focus the input inside the tap itself instead of one frame later; iOS raises its keyboard only for a focus made while the browser is still handling the tap, so the deferred focus left a caret with no keyboard until a second tap. A clear tapped while the keyboard is already up keeps it up, as before. Introduced in [#8158](https://github.com/facebook/astryx/pull/8158); final-state evidence: [#8247](https://github.com/facebook/astryx/pull/8247).
@vjeux