What's New
Release notes and changelog for all packages.0.7.6
New Features
- useAnnounce takes an optional
{hasReplace: true}. An instance created with it states one current state, such as a search's result count: each message it writes withdraws that instance's previous message while it has not been spoken yet, whatever their politeness, and is spoken at its own politeness, so input faster than a frame (a barcode scanner, dictation, automation) says only the latest. Messages from other instances, and from instances without it, still join. MultiSelector sends its result count, its create row and its empty-search message through such an instance, so fast typing no longer says1 result Create "Urg" Create "Urge" …; its selection changes keep their own instance and still join. This follows spec:AST-086 FR9 and FR13 (#9070). (#8640) - Adds three
@astryx.diffViewer.*keys to theencatalog for the labDiffViewer's large-change fold: its "Large change: N lines" label and its Show full diff / Hide full diff button. No existing string changes; locales without a translation fall back to English. (#9462) - FieldLabel: a tap on the label's info icon (
labelTooltip) opens its help without also toggling or focusing the control (component:FieldLabelFR9). Before, the tap that opened the help also activated the label's control, as a tap anywhere on a native label does: on a touch screen it focused the field, raising the keyboard, or toggled the switch or checkbox the label names, an unintended second action. Now a tap by finger or pen opens the help alone; a mouse click on the icon still activates the control like the rest of the label, and hover still shows the help. (#9089) - FieldStatus: the
tooltipvariant is deprecated and is removed in the next minor release. FieldStatus has no tooltip presentation: a direct<FieldStatus variant="tooltip">draws a plain message box with no tooltip, and your editor now marks it deprecated. To show a status message from a field's on-field icon, setstatusVariant="tooltip"on the field control instead; that stays supported. (#9196) Before:tsx<FieldStatus type="error" message="Required" variant="tooltip" />After:tsx<TextInputlabel="Name"value={name}onChange={setName}status={{type: 'error', message: 'Required'}}statusVariant="tooltip"/> - Adapt NumberInput's compact steppers to primary-pointer precision: hide them on coarse pointers and restore the field's themed end padding. Fine-pointer steppers are unchanged. (#8015) Compatibility: this is a non-breaking presentation adaptation. The public props and exports, numeric value and callback contracts, validation, direct entry, and keyboard stepping remain unchanged; existing NumberInput calls require no source or configuration migration. Coarse-pointer users enter the value directly instead of using the compact visual stepper aids.
- TextInput and TextArea tell a touch keyboard what the field holds. New props
enterKeyHint(what the Return key says: Search, Send, Next, Go, Done),inputMode(which keyboard: number pad, decimal pad, phone pad, web search, email, URL),autoCapitalizeandhasAutoCorrect, plushasSpellCheckon TextInput (TextArea already had it). TextInput'stypealso acceptssearch,telandurl. The value types are the new exported closed unionsEnterKeyHint,InputModeandAutoCapitalize, so TypeScript rejects any other value. Each prop renders the native attribute of the same name and nothing when unset, so existing fields keep the browser's defaults. (#8166) - A theme's
motiontakes two knobs beside the duration scale:tempo(0.75–1.5) scales every motion duration, andcharacter('crisp','standard'or'expressive') sets the new--ease-entranceand--ease-movetokens;--ease-exitstays the same at every character. Their types,ThemeMotionConfig,ThemeMotionKnobsandMotionCharacter, are exported. A theme without them renders exactly as before; a duration scale and explicit tokens win over the knobs, Spinner's and Skeleton's loops keep their timing under every tempo, and the press release fade follows tempo up to the 200 ms Reduce Motion cap under the person's setting. Springs don't read the knobs yet. The motion, token and theme-authoring docs and the theme template describe the knobs. (#8661) - TimeInput, DateTimeInput: the
hourFormatdefault follows the locale. This is a default change. The old default was always'12h'; the new default, whenhourFormatis unset, is theInternationalizationProviderlocale's hour cycle, so ade-DE,en-GB, orvi-VNapp shows "14:30" likeTimestampbeside it, whileen-USand an app with no provider keep "2:30 PM". To keep the old default, passhourFormat="12h". To honor a person's own 12/24-hour preference everywhere, put it on the provider locale (en-US-u-hc-h23). Twelve-hour text now uses the locale's own day period ("오후 2:30", "午後2:30", "2:30 p. m.") instead of a fixed English AM/PM, along with its digits and separator, and the typed field reads that text back. Fixes #8992. (#9022) - A
SearchSourcecan show results before its search settles.search(query, context)may callcontext.update(items)(new exported typeSearchContext) to show matches it already has, such as people the page loaded earlier, and then return the server's answer.BaseTypeahead,TypeaheadandTokenizershow each list for the current query, change the list at most once per keystroke, and add later rows only after the ones already shown, so the highlighted row never moves; the field stays busy and the result count is announced once, when the search settles. A later list that moves or removes shown rows is shown as given with a development warning. Sources that never callupdateshow one list per query as before, with two changes every field sees: option element ids now follow the item'sidinstead of its row index (tests that select options by an index-based id need updating), and a groupedTokenizerwithhasCreateshows its Create row after the groups instead of first. To show local matches at once, passdebounceMs={0}and delay the server request inside the source (spec:AST-092). (#7962)
Fixes
- A bottom-sheet DropdownMenu whose sheet preload fails (a dropped connection) no longer reports an unhandled promise rejection, and no longer keeps the failed load, so a module loader that retries loads the sheet's actions on the next open. (#8478)
DropdownMenuno longer rewrites its trigger's style on every render. Its trigger refs, and the trigger refusePopoverreturns, now stay the same function when the popover'sonShoworonHidechanges, so React stops detaching and reattaching the trigger, and a tooltip anchored to the same trigger keeps its place. Triggers that takeusePopover's ref directly (ComplexSelector's built-in trigger, DateTimeInput's date field and Breadcrumbs) get the stable ref too. (#9130)- A
Popoverin a Document Picture-in-Picture window now scrolls once that window gets too short for it or its content grows past it, instead of being cut off: it measures its overflow from the window it renders in, not the page. (#9098) - In Safari, content already gliding after a layout change no longer jumps ahead when a second change retargets it, such as a row that moves again while it is still moving, or a row inside a card that is itself gliding: the new glide started up to about 3 px ahead of where the row was drawn, more the later in its frame the change was made. A gliding element's place before a change is now read on the clock of every glide that carries it, its own and its gliding containers', so the new glide starts where the old one is drawn. (#9327)
AppShellis a layout root: the layout values its ancestors pass down stop at its root, so it lays out the same inside a paddedCard, aSectionor aLayoutas at the page root. Before, its internal Layout escaped a padded host's padding on all four sides, so in a paddedCardthat clips its overflow the shell's logo was cut at the inline start and its navigation and content at the other edges. A caller's own props and styles onAppShellstill apply; theme, color mode, direction and translations keep inheriting. (#9418)- With
height="fill", AppShell's main region can be scrolled from the keyboard when its content overflows and has nothing focusable (WCAG 2.1.1 Keyboard). Before, main was only the skip link's target (tabIndex={-1}): Tab passed it by, so long text, a report or a read-only page could not be scrolled without a pointer. Now, while main scrolls overflowing content, it is a stop in the tab order and keyboard focus on it draws the standard focus ring, inset; in an elevated shell with a top nav and an inline side nav, main then takes the surface's rounded top-start corner so the ring follows it. Tab entry moves on when the first focusable element inside main is a plain link or button; otherwise main is one stop before it. A main region that fits, andheight="auto"(where the page scrolls), are unchanged. (#8111) - DateInput ignores selections from an already-open disabled picker and blocks Reset's value change and month navigation while disabled, without dismissing the picker or moving focus. (#8813)
- DateRangeInput ignores calendar and preset commits after its open picker becomes disabled, without dismissing the picker or moving focus. Presets reflect the field's disabled state and reason. Enabled selection, clear behavior, and loading-only dismissal remain unchanged. (#9155)
- MultiSelector blocks selection and creation callbacks and Actions when it becomes disabled while its panel is open, without removing the focused control. (#9152)
- Selector ignores option selections after it becomes disabled, including selections from an already-open popup and pointer gestures started while enabled. Its trigger remains focusable and disabled values remain excluded from forms. (#9137)
- In forced colors (Windows High Contrast), a lone
Avatar's initials and default person icon now take the color around them, as the browser forces it, instead of always showing CanvasText: inside a control that paints itself disabled they show GrayText. Faces inside anAvatarGroupkeep CanvasText on the group's ring. Outside forced colors nothing changes. (#8819) - Badge: a badge with a label is now never shorter than one line of that label. With a larger text size, a badge's label grew while the badge kept its fixed height, so the label spilled out of the pill and white text on a colored badge became unreadable. The badge now grows with its label. At the default size nothing changes, a theme that sets the badge's height keeps that height there while its badges still grow with larger text, a color-only badge keeps its size at every text size, and a badge still shrinks and truncates in a container too narrow for it. (#8236)
- Dragging a
BottomSheetwith snap points up from a shorter detent, or back down past it, no longer flashes the sheet away from the finger. For one frame the sheet jumped by the height its scrolling area gives up at that detent (about half the screen at a half-height stop) and then snapped back. The height and position now change in the same frame. (#9193) - A BottomSheet opened from inside another sheet's content drags down to dismiss on its own. The covered sheet underneath no longer takes the gesture, so dragging the top sheet's grabber no longer moves or dismisses the sheet beneath it. (#8820)
- Calendar, DateInput, DateTimeInput: a month label that stands alone starts with a capital where the locale capitalizes one. In Spanish, French, Italian, Dutch, Polish, Russian and Ukrainian, Calendar's heading read "octubre de 2026"; it now reads "Octubre de 2026", following CLDR's stand-alone capitalization, as the weekday headers already use CLDR's stand-alone names. A two-month view capitalizes both months, and each month grid's name, the touch date fields' month headings and
useCalendarNavigation'smonthYearLabeldo the same. Dates in running text, such as a field's value, are unchanged, and so is every locale CLDR does not capitalize, Vietnamese included. (#9371) - Carousel's scroll area is a group named like the carousel, so a screen-reader user who tabs onto it hears where they are. It is a tab stop only while its content overflows; a carousel that fits no longer adds an empty stop. (#8155)
- ChatComposerInput: a tap on a pasted-text token opens its preview without raising the keyboard. Before, the tap that opened the preview also focused the composer around the token and placed the caret in it, which on a phone raises the on-screen keyboard over the preview. Now a tap by finger or pen stops at the token, so touch reaches the preview and its Expand action without the keyboard covering them, the operable path
architecture:interaction-modalityINV4 asks of every modality; a mouse click on the token still places the caret in the composer, and hover still opens the preview. (#9189) - A click inside an open Tooltip or HoverCard in a ChatComposer's body no longer moves focus to the composer's input. A click on the body's empty space still focuses it. (#9375)
- A press in a ChatComposerInput's own editor no longer closes its open trigger menu (the
@mention or/command list). Clicking inside the query keeps the menu showing; a click that moves the caret out of the query, a press anywhere else on the page and Escape still close it. (#9503) - Safari no longer slows down as a page fills a container with many children because of ChatMessage's avatar-spacing rule. The avatar's top spacing beside a named bubble is now judged from the message itself instead of from its siblings. It looks exactly as before. (#9438)
- CheckboxList: a group disabled with a
disabledMessagegives that reason to each checkbox as its description (aria-describedby), as well as to the group, so a screen reader announces it on the focused checkbox. A row's own description comes first. (#9168) - ClickableCard: a disabled link card no longer passes an undefined
hrefto the router link component, and a focused link card keeps focus when its disabled state changes. (#8659) - CodeBlock: in right-to-left layouts the collapsed disclosure chevron now points toward the inline end (left), as other disclosure chevrons do. Expanded, it still points down. (#9294)
- When a
Collapsiblecloses while keyboard focus is inside its content, for example from an owner-setisOpenor a group's value, focus moves to its trigger. Before, focus fell to the page, so a keyboard or screen-reader user lost their place (WCAG 2.2 SC 2.4.3). Focus anywhere else is not moved. (#9250) TypeaheadandTokenizerexpose their state on the combobox (WCAG 2.2 SC 4.1.2;component:FormLayoutFR5 and AR2). Before, the combobox had noaria-required, so underFormLayout defaultOptionality="required", where the visible "Required" marker is hidden, a screen reader announced a required field as optional; and an error status showed its message with noaria-invalid. Now the combobox setsaria-requiredfor the resolved required state andaria-invalidfor an error status. A caller's ownaria-requiredoraria-invalidstill applies when the field's own state is off. (#9034)- CommandPalette no longer shows its "Type to search" text after you have typed. While the first search is still loading, the list stays empty and the field's loading spinner shows; the no-results text appears once that search finishes with nothing. Clearing the field brings "Type to search" back. (#9420)
- Comments: the failure announcement spoken for a Comments error banner now comes from the
@astryx.comments.errorAnnouncementlocale entry, so it can be translated like the rest of the component's messages. (#7902) - ComplexSelector's popup content keeps its last rows clear of a bottom bar the app declares through
LayerProvider'sinset, instead of scrolling them underneath it, and its chevron turns at once when the person prefers reduced motion instead of animating its rotation. (#8551) - ComplexSelector: with
statusVariant="tooltip"the status message is no longer lost. The trigger row now shows the status icon as a focusable info-tip button that reveals the message on hover, keyboard focus, or tap, and the trigger is described by that message instead of pointing at an element that did not exist. Pressing the info-tip does not open the popup. (#9026) - A context menu that was never opened no longer mounts its menu surface; it mounts at the first open and shows as it attaches. A Table whose cells carry context menus (row expansion gives every body cell one) showed its first rows after a minute or more at 2,000 rows in Safari; it now shows them in a few seconds. (#9278)
- An app bundled into one esbuild file (no code splitting, as no-build pages are) no longer crashes on first render with a TypeError such as "Cannot read properties of undefined (reading 'useId')" or "(reading 'useEffect')", for example when it uses
ListorButton. Code-split apps are unchanged and still load Core's lazy modules on demand. (#9055) - DateInput, DateRangeInput and DateTimeInput no longer build their calendar while the popover is closed. Each closed field used to mount a full month grid at page load and keep it updated, so a form with many date fields paid that cost per field. The calendar now mounts when the popover opens and opens on the field's current value. Opening, focus and dismissal are unchanged. (#8902)
- A press in a DateInput's own text input, on its clear button or on its label no longer closes its open calendar. Clicking into the date text to fix a digit keeps the calendar showing; a press anywhere else on the page and Escape still close it, and moving focus from anywhere in the field (its text, clear button or calendar button) to another field now closes it too. (#9433)
- A press in a DateTimeInput's own time input no longer closes its open list of preset times. Clicking into the time text to fix a digit keeps the list showing; a press anywhere else on the page, moving focus away and Escape still close it. (#9459)
- A
Dialogrendered into a same-origin iframe through a portal now returns focus, when it closes, to the control in the iframe that opened it, as it does in the page. (#8381) - A disabled field that keeps its tab stop (TextInput, TextArea, NumberInput, Typeahead, Tokenizer, Selector, MultiSelector, and DateInput, TimeInput, DateRangeInput and DateTimeInput on every surface: popover, native and bottom sheet) now shows keyboard focus under forced colors, such as Windows High Contrast. Its focus border takes the system Highlight color there, as enabled fields' does. Nothing changes outside forced colors. (#9410)
- A disabled
Item,ListItemorTreeListrow with anhrefno longer navigates from a screen reader, Enter, or a link menu. Its link now has nohref,targetorrel, as a disabledLinkdoes, and it keeps the link role. (#9056) - Under a finger in Chrome, the page beside an open non-modal
Drawer(hasScrim={false}) scrolls again. The panel clipped its content withoverflow: hidden, which made it a scroll container, and Chrome held a drag on the page beside it in that container's overscroll containment, so the page did not move. It now clips withoverflow: clip, which clips the same way without a scroll container. The panel's content area still scrolls on its own, and a modal drawer is unchanged. (#8636) - The development warning for passing both
buttonandrenderTriggertoDropdownMenunow namesrenderTrigger; it named atriggerprop that does not exist. The docs match the component too:buttonis mutually exclusive withrenderTrigger, the private menu radius defaults to--radius-container, and a disabledDropdownMenuCheckboxItemorDropdownMenuRadioItemtakes no focus — the arrow keys, typeahead, and the pointer highlight skip it — while it stays in the accessibility tree as disabled. (#7517) - A keyboard-focused
DropdownMenurow now shows the standard focus ring, drawn inside the row, in every color mode. Rows showed focus only with a translucent background, which forced colors (Windows High Contrast and similar modes) replace with the page color, so a keyboard user there could not tell which row Enter would activate. The ring follows the last input: after a key press it marks the focused row, including a row the mouse then moves focus to; after a mouse or touch press it does not show. Action, destructive, checkbox, radio and sub-menu rows all show it, including inContextMenuand breadcrumb menus. AContextMenuopened by right-click or long-press focuses its first row without the ring; one opened from the keyboard shows it. (#7517) - The anchored
DropdownMenunow reflectsdata-presentation="popover"on itsdropdown-menutarget, as the bottom sheet already reflectedbottom-sheet. A theme rule written forpresentation:popover, which the docs list as a visual prop of that target, now applies. (#7517) DropdownMenuandMoreMenunow forward the caller's ref to the trigger button in the bottom-sheet presentation (architecture:public-component-apiINV8). Before,presentation="bottom-sheet", orpresentation="adaptive"on a compact touch screen, replaced thebutton.ref(and therefthatMoreMenupasses) with an internal ref, so a caller's ref stayed empty. The popover presentation already forwarded it. Apps need no code change. (#8898)DropdownMenu,MoreMenuandContextMenurender a submenu for a data item with nesteditemsinside a{type: 'section'}, as they do at the top level. Before, such an item rendered as a plain row with no flyout and noaria-haspopup, although its type allows nesteditemsthere; the bottom sheet on a phone already showed it as a submenu. (#8858)- With an
animatedLayouthandle, a Collapsible or a TreeList row closed while it opens, or opened again while it closes, continues from what it shows: the content's edge stays on the content after it on every frame, instead of jumping back to fully shown or hidden. Under Reduce Motion with a touch pointer, where the content cross-fades instead, a reversal still starts its fade over. (#8721) - Field:
FieldStatusPlacement, the type of every field control'sstatusVariant('attached' | 'detached' | 'tooltip'), is exported from@astryxdesign/coreand@astryxdesign/core/Field, so a wrapper component can type astatusVariantprop it forwards. (#9368) - Enabled Field inputs (TextInput, TextArea, NumberInput, Selector, MultiSelector, Typeahead, Tokenizer, and the date and time inputs) now show keyboard focus under forced colors, such as Windows High Contrast. Forced colors drop the inset focus shadow and repaint every border in one system color, so a focused field looked the same as one at rest. A focused field's border now takes the system Highlight color there, with or without a status. Disabled fields, which stay focusable, don't get it yet. Nothing changes outside forced colors. (#9392)
- FieldStatus wraps a long unbroken word in a validation message, such as an email address or URL echoed from the field, inside the message box instead of painting it past the field's edge where its end could not be read. (#9126)
- TextArea, Typeahead and Tokenizer: a caller's
aria-labelledbyno longer replaces the field's own label. Before, it was the only name the control had, solabel="Notes" aria-labelledby="billing-heading"named the textarea "Billing". Now the caller's ids follow the field's own label ("Notes Billing"), as TextInput, NumberInput, Selector and MultiSelector already do. A Typeahead inside an InputGroup, which ignored the caller's ids altogether, is now named by the group, its label, then the caller's ids. The visible label stays in the accessible name (WCAG 2.2 SC 2.5.3 Label in Name;family:input-fieldsFR10.1). Fields without a calleraria-labelledbyare unchanged. No API changes. (#8862) - FileInput with
statusVariant="tooltip"keeps its status button, and the message it reveals, in dropzone mode and while the field is busy (loading or uploading), instead of dropping it and leaving the field's description pointing at nothing. (#9134) - FileInput: a caller's
aria-describedbyand otheraria-*props now reach the trigger button, the field's focusable control. Before they were set only on the hidden native input, which isaria-hiddenand never focused, soaria-describedby="hint"was never read ("Report" announced without "PDF only, up to 10 MB"). The caller's ids are now joined to the trigger's own description ids, first. The props the trigger composes itself (aria-label,aria-labelledby,aria-invalid,aria-busy,aria-disabled,aria-hidden) are not copied. Seefamily:input-fieldsFR10.1. No API changes. (#9031) - When several picked or dropped files break
acceptormaxSize,FileInputnames every rejected file and why in its status message, not only the first (WCAG 2.2 SC 3.3.1). The messages are listed in the active locale. Going overmaxFilesstill reports the limit, "Maximum N files allowed". (#9043) - Inside
<FormLayout defaultOptionality="required">, FileInput and Slider now tell screen readers they are required even without their ownisRequired, like the other fields.isOptionalstill opts a field out. (#9053) - ButtonGroup and InputGroup: the rule that rounds a group's last member no longer slows down filling a container in WebKit (as measured), on any page, groups or not. In WebKit, inserting 10,000 children into one element took about 1.15 s with the old rule on the page and about 10 ms with the new one. Corners look exactly as before: only the last member, skipping trailing popovers, templates and dialogs, rounds its trailing corners. (#9394)
- Include the visible heading in SideNavHeading and TopNavHeading menu button names, with or without heading links. Keep the translated generic name when TopNavHeading has no heading. (#9329)
- Tooltip and HoverCard: a tap on a disabled
Button,IconButtonorToggleButton, or a disabled menu item, now opens the tooltip that explains why it is disabled, and nothing activates. Before, withtouchTrigger="auto"(the default), the tap counted as the control's own action, so on a touch screen the disabled reason could not be reached (spec:AST-085FR5,architecture:interaction-modalityINV4). Anaria-disabledcontrol now performs no action, and a tap on a label for a disabled control opens its reason too. A tap on a disabled control inside another acting trigger, such as an option row or a link-role card, now opens that trigger's tooltip or hover card. Taps on enabled controls,touchTrigger="tap"and"none", and mouse hover are unchanged. (#8207) - Touch press feedback now hears scrolls and page hides on the window's capture phase, where its pointer listeners already were. Under an app's window-capture
stopPropagation, or a document-capturestopImmediatePropagationregistered before Core, a finger's pressed look now ends when the content under it scrolls, and every pressed look ends when the page is hidden. (#8360) - TypeScript users applying
interactionOverlayStylesthrough an Astryx component'sxstyleno longer get a type error. The touch-press properties of each variant (animationName,animationDuration,animationTimingFunction,animationFillMode, and the colour variants'backgroundImage) now carry their CSS value types instead ofunknown. The generated CSS is unchanged. (#9440) - A disabled swipe action on an
Itemrow now stays focusable while the row is swiped open. Before, it rendered a<button>with the nativedisabledattribute, so Tab skipped it and a keyboard or screen-reader user could not reach it to learn it exists. Now it exposesaria-disabled="true"and keeps its Tab stop, while a click, Enter or Space still runs noonActivate, leaves the row open, and does not reach the row's ownonClick(spec:AST-085FR1, FR2). No API changes. (#9211) - The arrow-key hint of TabList, Toolbar and SegmentedControl no longer appears, or gets used up, when focus lands in content a tab or toolbar button opens through a portal, such as a sheet, dialog or popover. It still shows the first time keyboard focus enters the row itself. (#9362)
- A tall tooltip, or any layer that keeps clear of its trigger, no longer covers the trigger for an extra frame when the page scrolls on a busy device. The layer re-checks its place in the frame after the scroll, before that frame paints, so the trigger stays visible from the second frame on. (#9123)
- useLayer: a show that a browser-run popover hide refuses (Chromium 156 throws an
InvalidStateError) is replayed once that hide has ended, so the layer ends shown. For example, when the browser's own Escape closes a light-dismissible layer, the tooltip on the button that opened it now shows instead of failing. (#8543) - A press inside an open layer (a popover, tooltip, hover card, menu, dialog, drawer, lightbox, mobile navigation, bottom sheet or toast) no longer runs click, pointer, mouse or touch handlers on the elements around where the layer is written. Before, a click inside a menu written inside a clickable card or row could also activate that card or row. Handlers inside the layer, capture-phase handlers, and document and window listeners still receive the press. A handler that needs presses inside a layer belongs on the layer's content. (#9497)
SelectableCard: a click inside an open layer within the card (such as a popover's content) no longer toggles it. Until the next minor, the caller'sonClickstill receives that click, now during the capture phase, so before the layer's own handlers. - Link:
maxLinesnow truncates when the link sits in a line narrower than its text. The link, as an anchor or a button, stops at its container and its label draws an ellipsis, instead of growing to its whole text and being clipped with no ellipsis. (#9059) - A caller's
data-colorno longer replaces the oneLinkreflects for theme targeting (architecture:public-component-apiINV5,LinkFR11). Before, caller props were spread after the theme attributes, so passingdata-colorchanged what theme rules saw on the root even though the realcolorprop was unchanged. This holds for the anchor, button and disabled forms. Other callerdata-*attributes still reach the root. (#9157) - A finger held on a DropdownMenu trigger may drift up to 13px on each axis and still open the menu under every primary pointer, a phone's, a tablet's and a touchscreen laptop's alike, as AST-094 FR29 allows; it cancelled past 10px. No menu, row or trigger reads the pointer query. (#8360)
MobileNav's header row grows with its content. It was a fixed one-bar height, so a header taller than one row (a title with a search field under it, or a title that wraps at a larger text size) overflowed the row: the bottom border ran through it and the content ran into the first navigation item. The row is now at least one bar high, so a one-line header looks as before.SideNavin drawer mode, which passes itsheadertoMobileNav, gets the same fix. (#8865)- Components rendered into a same-origin iframe or a Document Picture-in-Picture window now read the last input in their own document for their keyboard focus rings and keyboard highlights (Slider, MultiSelector, DropdownMenu, ChatComposer, CommandPalette, panel search fields, menus), and for the ring on focus they move themselves. On the page, behavior is unchanged. Where an overlay returns focus on close is unchanged. vjeux wrote the original per-document fix, for Dialog (#8381); this extends it to every reader. (#9148)
- In the DateInput and DateTimeInput bottom-sheet calendars, a month arrow clicked or tapped as the previous arrow's scroll is ending now brings the calendar to the month its title names in Safari, instead of back to the previous arrow's month. (#8513)
- In the DateInput and DateTimeInput bottom-sheet calendars, a month arrow no longer sets the calendar paging on by itself in Safari when the page stalls for a moment right after the tap; the calendar moves one month and stays there. (#8513)
- MultiSelector: the default count text on the trigger (
triggerDisplay="count", for example "2 selected") now comes from the message catalog (@astryx.multiSelector.selectedCount), so it is translated and can use plural forms under any locale.formatValuestill replaces it. (#9020) - In a SideNavHeading or TopNavHeading menu built with NavHeadingMenu, one ArrowDown or ArrowUp now moves focus one item. It used to move two, skipping every other item, and in a two-item menu ArrowDown never moved focus. (#9019)
- Fix FileInput to prevent file picker activation and file selection while busy. Clear drag-over highlighting when disabled or busy, and expose the busy trigger as disabled to assistive technologies. (#9167)
- NumberInput: with
formatValue, tabbing into the field keeps its text selected, so typing replaces the value. Before, the editable text replaced the formatted text after focus and collapsed Tab's selection to the end, so with1,500,000shown, Tab then7gave15000007and committed it on blur. Now1,500,000becomes a fully selected1500000and7replaces it. A click still places the caret where it landed. Fields withoutformatValueare unchanged. No API changes. (#9033) - Following an
Outlinelink moves focus to the chosen section, as a native in-page link moves the focus starting point, so the next Tab continues from that section instead of jumping back to the top of the page. The section is focused without scrolling, so Outline's own scroll is unchanged (WCAG 2.2 SC 2.4.3 Focus Order). (#9045) - Dismissing a file picker (Escape, or Cancel in the chooser) inside a
Drawer,MobileNavorLightboxno longer closes it and loses what was in it. Only a close request fired at the surface itself closes it, asDialogandBottomSheetalready do. (#8855) - A
Dialog,DrawerorBottomSheetthat is open on the server now renders closed until hydration, and opens right after it where it rests, with no entry motion, as anything present on page load does; its later opens and closes animate as before. Before, it painted open over a live page witharia-modal="true"but no modal state: the page under it stayed interactive, a sheet's invisible host could swallow clicks, and assistive technology was told a modality that didn't exist (WCAG 2.2 SC 4.1.2). ABottomSheetSwitcherwhose active sheet is set on the server is covered too. Client-rendered overlays are unchanged. (#9360) - A determinate ProgressBar keeps moving to its new value while a script runs. The fill animated its
width, which lays out and repaints on the main thread every frame, so a value change stalled for as long as the page ran JavaScript and then jumped. The fill now spans the track and slides into place with a transform that the browser animates on its compositor, in Chromium and in Safari, laying out and painting nothing per frame. Under reduced motion a new value now lands at once, on every pointer. Otherwise duration, easing, colors, marks and right-to-left drawing are unchanged (the fill mirrors with the bar's own direction, so a bar in a left-to-right region of a right-to-left page still fills from the left); the track now clips its fill to the rounded rail in both modes, so below about one track height of fill the leading end follows the track's curve instead of drawing a narrower full-height capsule, and a runtime change of the bar's direction slides the fill across to the other side instead of jumping there. (#8196) - A disabled
RadioListItemno longer runs a caller'sonClick(spec:AST-085FR2). Before, a radio in a group disabled with adisabledMessagestays focusable througharia-disabledrather than nativedisabled, so the browser did not silence it and the handler still ran on a click on the radio, on Space, and on an arrow key onto it. It still refused to select. An enabled radio is unchanged: itsonClickstill runs. (#9120) - RadioList: a group disabled with a
disabledMessagegives that reason to each radio as its description (aria-describedby), as well as to the radio group, so a screen reader announces it on the focused radio. A radio's own description comes first. (#9169) - RadioList and Switch: a required field no longer reads as "invalid entry" to screen readers before the user has answered. Each required radio and a required switch take their invalid state from
status. (#9042) useResizable(and every component that uses it, such asSideNav) no longer reads the window size again after each render it commits. That read forced a layout of the whole page inside every commit, so a tab switch under anAppShellwith aSideNavpaid for it on slow devices. The window is still read during render, and every size, bound and reported maximum is unchanged. (#8857)- A
Tablecolumn-resize handle is named by its column's visible text when the header is a node, such as<span>Amount (EUR)</span>, instead of by the column key. The key remains the fallback only for a header with no text. (#9057) useScrollOverflowmeasures again when the container's content changes with the container keeping its size: a child added, removed or resized, or a new gap or padding. Carousel's scroll area, a tab stop only while its content overflows, and its edge buttons and fades follow slides added or removed and a slide that grows; TabList's fades follow its tabs the same way. (#8155)- SegmentedControl: a control disabled with a
disabledMessagegives that reason to each segment as its description (aria-describedby), as well as to the group, so a screen reader announces it on the segment that has focus. The control also always keeps one Tab stop: the selected segment, even when it is itself disabled, else the first segment not disabled on its own, else the first. (#9176) - SegmentedControl: a disabled control, or a disabled selected segment, keeps the control's Tab stop. Before, a control disabled without a
disabledMessagehad no Tab stop and ignored the pointer. A selected segment that was itself disabled lost the stop to another segment, and once the stop had moved there, selecting a third segment left it behind, so Tab re-entered on an unchecked segment. Now the selected segment always holds the one Tab stop, announced as disabled (aria-disabled) when it is, and nothing can be selected while disabled. (#9314) - A disabled
SegmentedControlItemno longer runs a caller'sonClick(spec:AST-085FR2). Before, the segment refused to select but still called the handler on a click, and on Enter or Space for the selected segment of a group disabled with a reason, which stays focusable. This covers a segment disabled by its ownisDisabledand one disabled by its group. An enabled segment is unchanged: itsonClickstill runs first and can still cancel selection withpreventDefault(). (#8989) - Selector, MultiSelector: pressing another field while the list is open now leaves focus in that field. Before, the list's close handler moved focus back to the Selector's trigger, so the next key went to the closed Selector (a letter could change its value through type-to-select). Escape, picking an option, or a press on nothing focusable still return focus to the trigger, and a MultiSelector with
renderTriggerstill returns focus to the caller's control on every close. (#9018) - A disabled
SideNavItemstays focusable. Before, it rendered a<button>with the nativedisabledattribute, so Tab skipped it and keyboard and screen-reader users could not reach it, and an item that became disabled while focused dropped focus to the page. Now it exposesaria-disabled="true"and keeps its Tab stop, while a click, Enter or Space still runs noonClick, does not navigate, and does not close the mobile drawer. In a collapsed rail, a disabled item's label tooltip now opens when Tab focuses it and describes the focusable control rather than its row. This meets the focusable-disabled requirement in spec:AST-085 (FR1, FR2, FR4, FR5). No API changes. (#9102) - When a collapsible
SideNavcollapses and takes the keyboard focus with it, focus now moves instead of falling to the page, where a keyboard or screen-reader user lost their place (WCAG 2.2 SC 2.4.3). From a row the collapsed rail does not render, such as an item without an icon, focus moves to the collapse toggle, or, with no toggle in the SideNav, to the nearest row still in the rail. On a row the rail keeps, focus stays on that row, and a header or footer control the collapse keeps or re-renders under the same name keeps it. From a header or footer control the collapse removes or replaces under another name, or the resize handle of aresizableSideNav, focus moves to the collapse toggle, or, with none, to the first row. Focus the collapse does not take is not moved. (#9249) - A
resizableSideNavkeeps its nav and items mounted when it collapses or expands, as a plain one does. Before, every collapse remounted them, so an open nested group closed and item state reset. (#9290) - SideNav (
footerIcons,topContent), SideNavHeading (icon,headerEndContent), SideNavItem (endContent) and SideNavSection (endContent): a slot whose value is0showed a stray "0" beside its slot, or nothing at all. Now each slot follows the shared presence check. Empty values (null,false,'') render no slot, as an omitted one does.0renders inside its slot as content, including a collapsed rail's icon-only heading and the footer and top areas around it. (#9498) - Slider: a press on the mark label of two coincident thumbs' shared value now goes to the upper thumb, as a press on the thumbs does, so a press that never moves leaves focus on the same thumb wherever it lands. Before, a press on that label went to the lower thumb, which the upper one covers. (#9184)
- Slider: a range slider whose two thumbs sit on the same value can be dragged apart again. Only one of the two thumbs can travel toward where the pointer goes: a press on the track beside them picks the thumb on its side, and a press on the thumbs themselves waits for the pointer to move, so the direction of that first movement picks the thumb, which takes the drag's focus, pressed paint and value tooltip. Such a drag always follows the pointer: once the pointer passes the other thumb, the dragged thumb stops against it and the other one takes the drag, so a first step that drifts the wrong way never sticks it. Before, two thumbs at the maximum could not be dragged down, and a press on the track above two coincident thumbs moved neither. (#8151)
- Slider: a range slider's thumb names ("Minimum value" and "Maximum value", announced to screen readers) now come from the message catalog (
@astryx.slider.minimumThumb,@astryx.slider.maximumThumb), so they follow the app's locale. (#9023) - Published packages no longer include repository test and benchmark files, reducing install size without changing exports. (#9153)
- More slots treat
'',falseandtrueas empty, the way React renders them, instead of drawing an empty wrapper: ChatSystemMessage'sicon, Item'sstartContent,endContentanddescription(so a ListItem or menu row gains no blank lane), and MetadataList'stitleand MetadataListItem'sicon.0still counts as content and shows "0". (#9204) DropdownMenuGroup'stitleandBadge'slabelnow use the sharedisRenderablecheck, sonull,undefined,true,falseand''count as rendering nothing, and0still counts as content. ADropdownMenuGroupwithtitle={true}no longer renders an empty heading that names the group.Badgeis unchanged (thanks @vjeux, #8236). Other slots are unchanged. (#9160)- More slots treat
'',falseandtrueas empty, the way React renders them, instead of drawing an empty wrapper: TreeList'sheader(a header that renders nothing no longer names the tree, so it keeps itsaria-label), TreeList items'startContentandendContent, TopNavMegaMenu'sitemsandfeatured, Table headeraftercontent, and OverflowList's measured overflow indicator.0still counts as content and shows "0". (#9206) - Many components that show built-in text are smaller. Each one now carries only the English for its own strings instead of every Core string, so a component such as Button loads about 7 KB less (gzip) and a new string elsewhere in Core no longer makes it bigger. Table (and Markdown, which renders it), Chat, PowerSearch, CommandPalette and the date and time inputs still carry every Core string for now. Nothing you see changes: every built-in string still shows the same English, translations and overrides resolve as before, and
useTranslator,InternationalizationContextand@astryxdesign/core/locales/en.generated.jsstill reach every Astryx string. (#9429) - Table, Markdown, Chat, CommandPalette and the date and time inputs are smaller too. Each now carries only the English for its own strings instead of every Core string, about 7 KB less (gzip) each. PowerSearch still carries every Core string, because a custom operator's
i18nKeycan name any Astryx key. Nothing you see changes: every built-in string shows the same English, and translations and overrides resolve as before. (#9452) - TextArea: a
startIconof0showed a stray "0" beside the start-icon slot, with no padding reserved for it. The slot and its padding now follow one presence check: empty values (null,false,'') render no slot, and0renders inside the slot like any other content. TextInput uses the same check, with no visible change. (#9443) - In a clickable
Stepper, a disabledStepnow keeps its button: it stays in the tab order, is announced as unavailable (aria-disabled), and keeps focus if it becomes disabled while focused, but still does not activate. Its description (the reason it is unavailable) describes the button (spec:AST-085FR1, FR4, FR5). Before, it rendered as plain text, so keyboard and screen-reader users could not find it or tell it was unavailable. (#8867) - A disabled
Switchno longer runs a caller'sonKeyDownoronKeyUp(spec:AST-085FR2). Before, the switch stayed focusable througharia-disabledinstead of nativedisabled, so a key pressed on it still reached those handlers, while itsonClickwas already withheld. It still refused to toggle. An enabled switch is unchanged: its key handlers still run. (#9122) Tablenames say what they belong to (WCAG 2.2 SC 4.1.2 and 2.4.6; the APG sortable table pattern underspec:AST-020FR15;spec:AST-025FR12). (#9047)- A sort button was named "Sort by Name", or "Sort by Name, sorted ascending" with "priority 2 of 3" in multi-sort, and that phrase replaced the column header's name. It is now named by its column's text, so the header keeps that name; the direction comes from the header's
aria-sort, and while several columns sort, each button is described by its priority ("Priority 2 of 3"). - The scroll region was a group named "Table" on every table. It now takes the table's own name (its
aria-labelledby, else itsaria-label), and "Table" only for an unnamed table.
- A sort button was named "Sort by Name", or "Sort by Name, sorted ascending" with "priority 2 of 3" in multi-sort, and that phrase replaced the column header's name. It is now named by its column's text, so the header keeps that name; the direction comes from the header's
- TabList: pressing or arrowing to a tab in a scrolling strip no longer measures the strip inside the press. Focusing the tab already scrolls it into view, so the check that keeps the selected tab whole now runs in the next frame instead of forcing the new selection's style and layout before the press can paint. (#8856)
- Text and Heading: a long unbroken word, URL or ID in text that isn't truncated now wraps instead of running past its container, so in ordinary flow a phone-width page (320 px) no longer scrolls sideways. Ordinary text lays out exactly as before, and truncation (
maxLines) is unchanged. Inside a flex row, the flex child still needsmin-width: 0. Text and Heading now setoverflow-wrapthemselves, so a container you style withoverflow-wrap: anywhereno longer reaches their text; Astryx's own containers (CommandPaletteEmpty, Toast, FieldStatus, Banner) pass theiranywherewrap through. (#9351) - TextArea: the
maxLengthcharacter counter now comes from one catalog message (@astryx.textArea.counter), so its numbers use the locale's number format and translators can change the order or separator. In English a limit of 1,000 or more now shows grouped digits (62/2,000instead of62/2000). (#9025) - TextInput: the clear button no longer shifts inward when the field turns busy. The busy Spinner now sits inward of the clear button, as in Typeahead and Tokenizer, so a user reaching for the button while a search runs does not miss it. No API changes. (#9027)
- ProgressBar target marks expose their label as an accessible name before the tooltip loads, while keeping keyboard focus and hover/focus tooltips. (#9276)
- Timestamp keeps a caller's
aria-labelon relative output and a caller'stabIndexwhile its hover card is attached. Before, the full-date name and the card's tab stop overwrote them, so a timestamp named for its context (for example "Posted 5 minutes ago") lost that name, and one taken out of the tab order came back into it. Without a caller value, nothing changes. (#8726) - Toast: a
Themeinside toast content shown by the fallback viewport (noLayerProvider) now themes only its own subtree. It no longer rewrites the page's<html>theme as if it were the app's rootTheme. First fixed in #5617. (#9253) - A toast that is closing when a new toast takes its visible place under
maxVisible, or that the same handler pushes out and then dismisses, leaves the stack at once. Before, it came back later as an invisible, empty row that kept the notifications landmark, took one of the visible places, and let F6 move focus to its hidden dismiss button. A secondcollisionBehavior: 'ignore'toast with the sameuniqueID, raised in the same handler as the first, is now dropped unannounced, as it already was once the first had rendered. When a control inside a toast raises toasts and then dismisses its own toast, focus moves to a toast that shows, the new one included, instead of to the notifications region. (#8051) - Toast: a toast's auto-hide timer stays paused while any pause condition still holds. Before, the pointer leaving the card, focus leaving it, or the window regaining focus resumed the timer even if another condition was still active, so a toast could hide while focus was on its action or the pointer was over it. Focus moving between the toast's own controls also keeps it paused. (#9016)
- Toast: dismissing the last toast after reaching it with Tab or a click returns focus to where it was before, instead of dropping it to the page. (#9039)
- A caller's
aria-pressedordata-is-pressedno longer replaces the pressed stateToggleButtonreflects (architecture:public-component-apiINV5,ToggleButtonFR12). Before, caller props were spread last, so passing either attribute made assistive technology and theme rules see a state that did not matchisPressed.ToggleButtonnow ownsaria-pressedand the reflecteddata-is-pressedanddata-elevation. Other callerdata-*attributes still reach the root. (#9159) ToggleButtonGroupacceptsclassName,style,id,aria-*,data-*and event handlers, and passes them to its group element. The group keeps its ownrole,aria-labeland theme target. (#9040)- A disabled
Tokenreflects its state on thetokentheme target (data-disabled) in every structure, so a theme can style it. A disabled link token keeps a focusable link announced as disabled (aria-disabled="true", nohref), instead of becoming plain text with no tab stop. (#9037) - A
Tokenwith anhrefnow calls a caller'sonClick(architecture:public-component-apiINV5,TokenFR3). Before,onClickwas dropped wheneverhrefmade the token a link, so the handler never ran on a click. This covers the link token and the link token with a remove button, where a plain click on the token surface runs the handler once, a Cmd/Ctrl-click or middle click on the surface opens the link in a new tab without running it, and a click on the Remove button does not run it. Navigation is unchanged, and callingpreventDefaultin the handler still stops it. (#9205) - The inline
TokenizerClear all button announces "All items removed", once, as the touch sheet does, so a screen reader user learns the selection was emptied.PowerSearch's Clear all announces its own words, "All filters removed". (#9038) - Tokenizer: the inline create row now takes its
Create "…"label from the@astryx.tokenizer.createmessage, the same one the bottom sheet uses, so it follows the provider's locale instead of always reading in English. Fixes #8931. (#9029) - A link in a Toolbar (such as a Button with
href) now shares the toolbar's single tab stop. Arrow keys reach it like any other control, and it no longer adds a second Tab stop to the row. (#8921) - Tooltip: under the default
focusTrigger="auto", keyboard focus opens the tooltip of a trigger that was out of the tab order when the tooltip attached. A Button or IconButton in a Toolbar or ButtonGroup whosetooltipwas set after mount, or any roving-tabindex member rendered withtabindex="-1", now shows its tooltip when the arrow keys reach it. Whether focus counts is decided when it arrives, so a focusable trigger the old check missed, such as a<summary>, opens too. Focus inside a trigger that is not focusable still does not open it. (#9366) - A click inside an open Tooltip or HoverCard no longer activates the card, row or field around its trigger: a FileInput no longer opens its file picker, and a ClickableCard, SelectableCard, Token, or Item, TreeList or Table row no longer activates. Links and buttons inside a HoverCard keep working. (#9252)
TopNavMenuandTopNavMegaMenunow forward theirrefto the trigger button in drawer mode (architecture:public-component-apiINV8). Before, only the desktop popover trigger received the ref, so a caller's ref stayed empty whenever the menu rendered inside the mobile drawer. Apps need no code change; the desktop trigger and every other prop are unchanged. (#8897)- TopNavMegaMenuFeaturedCard: in right-to-left layouts the link arrow now points toward the inline end (left) instead of backwards. The link's text and accessible name are unchanged. (#9317)
- TopNav (
heading,startContent,endContent), TopNavHeading (logo,headerEndContent), TopNavMegaMenuItem (icon), TopNavMenu drawer items'iconand NavHeadingMenuItem'sdescription: a slot whose value is0showed a stray "0" beside its slot. Now each slot follows the shared presence check. Empty values (null,false,'') render no slot, as an omitted one does: an emptycenterContentorstartContentno longer switches the bar to its center layout, shows the mobile-bar menu toggle or opens an empty drawer section.0renders inside its slot as content. (#9500) - Where the primary pointer is fine (a mouse, a trackpad, a touchscreen laptop, a desktop pen tablet), the press feedback controller no longer registers a touch listener: it reads the primary pointer at the first finger or pen press and keeps its
touchcancellistener only while that pointer is coarse. (#8360) - When a
TreeListrow collapses while keyboard focus is inside its children, for example from anitemschange, focus moves to that row (the outermost one when nested rows collapse together), which then holds the tree's Tab stop unless it is disabled (a disabled row takes focus, and the stop goes to the tree's first enabled row if the collapse removed the row that held it). Before, the focused row disappeared and nothing held focus, so a keyboard or screen-reader user lost their place (WCAG 2.2 SC 2.4.3). Focus anywhere else is not moved. (#9251) - ChatComposerInput's trigger menu announces its "Searching…" row through Core's shared busy announcement, like other busy controls: once per search, not repeated while typing continues, and not at all when results arrive first. Inside a native modal dialog an app renders without Astryx, it is now heard inside that dialog. (#9154)
TypeaheadandTokenizer: after the search source is replaced, pressing ArrowDown on the closed field loads the new source (its focus entries, or the typed query against it) instead of opening the old source's list. (#9166)- A
TypeaheadorTokenizerdisabled with a reason (isDisabledwithdisabledMessage) no longer opens its results from ArrowDown or a click. ATypeaheaddisabled this way also no longer accepts a pick by Enter or a press, even from a list that was open before it became disabled (aTokenizeralready refused those). Escape or Tab still closes such a list. (#9036) - Typeahead, Tokenizer, PowerSearch: a disabled field keeps its tab stop. Before, a field disabled without a
disabledMessagerendered a natively disabled input, so Tab skipped it and screen-reader users moving by focus never reached it. Now the input is announced as disabled (aria-disabled), stays read-only, opens and picks nothing, and shows a focus ring under keyboard focus. A search still in flight when the field becomes disabled is dropped: it opens, announces, and spins nothing. A Tokenizer or PowerSearch withtokenOverflowBehavior="unfocusedLayer"and nodisabledMessagekeeps its natively disabled input for now. (#9275) - Type-to-select ignores accents in every locale. Pressing
dnow reaches "Đào",areaches "Ánh" and "Åsa",nreaches "Ñandú",lreaches "Łódź", andınow reaches "Isparta" and "İzmir". This applies to a closed Selector and to open DropdownMenu, ContextMenu, MultiSelector and TreeList lists, and to the publicuseTypeaheadanduseTreeFocushooks. Before, a key typed without the mark skipped every item that starts with the marked letter. Matching ignores case, the combining accents U+0300–U+036F, the stroked letters đ ł ø ħ ŧ ƀ, and Turkish dotted and dotless i. It works the same way in every locale, because type-to-select is navigation, not sorting. When you type the accented letter itself, an exact match comes first. For Turkish, ı pairs with I and İ with i. A combining mark typed first is ignored; typed after a letter, it is part of that letter. Sorting and search filtering are unchanged. This meetsarchitecture:internationalizationINV17. No API changes. (#8864) - A press in a Typeahead's or Tokenizer's own text input, or on its buttons, no longer closes its open list. Clicking between two letters to fix a typo moves the caret and keeps the matches showing; a press anywhere else on the page still closes the list, and Escape still does. (#9367)
Tokenizer: an open list reloads when the tokens change, so it shows current choices instead of the old ones — a token removed with its button is offered again, and a value set from outside is no longer listed. (#9416)- With a value, a
Typeahead's Tab stop is the value's token button (WCAG 2.2 SC 2.4.6 and 4.1.2). It was named by the value alone ("Apple"), so screen reader users could not tell which field it belonged to. It is now named by the field label and the value ("Fruit Apple"), and described by the field's description and status. (#9049) A clickableTokenpassedaria-labelledbyandaria-describedbyto its root, a generic element where they named nothing. It now passes them to its inner button, the element that owns its action. Every other structure keeps them on its root. - useTheme:
modeis always'light'or'dark'. A mode outsidelight | dark | system, such as a stale persisted preference, now resolves through the OS preference like'system'instead of being returned as is. First fixed in #5617. (#9254) - Dragging a picker wheel with a mouse now commits the value when the button is released, as a finger's drag does. Before, the wheel committed every row it passed while the button was still down, so in DateInput the calendar behind the month and year wheels changed under the hand. This applies to the wheels in the TimeInput, DateTimeInput and DateInput bottom sheets. Touch, keys and a click on a row are unchanged. (#8483)
Performance
- Calendar, DateInput and the other date components now reuse one date formatter per locale and format instead of building one for every label they show, so rendering a month (42 day labels) no longer builds 42 formatters. (#8335)
useResizablewithautoSaveId(andSideNavwithresizable={{autoSaveId}}) now saves a dragged size tolocalStorageonce, when the drag ends, instead of on every pointer move. Every write reached each other open tab of the site as astorageevent, so one drag sent dozens of them. The storage key, the stored format and the size saved at the end are unchanged, and keyboard steps,resize(),collapse()andexpand()still save at once. (#7782)- Table: when nothing in a table depends on a row's position, re-sorting it no longer re-renders every row; the rows only move. On a 1,000-row table this is about a tenth of the work a sort click does. This applies to a table that has an
idKey, sets neitherrowCountnorrowIndexStart, and uses neitheruseTableRowIndexnor a plugin that transforms body rows (selection, row expansion, grouped rows, tree data). Those tables still re-render their rows on a sort. (#9234) - Pages that mount many truncated
TextandHeadingelements at once mount faster. Each one used to measure whether its text overflows while React was still committing the page, so every measurement forced its own style and layout pass; they now measure right after the commit, all of them together, so the page reads layout once. The ellipsis, the line clamp and the full-text tooltip are unchanged. (#9013)
Documentation
- Source comments in the BottomSheet gesture and mobile keyboard code are shorter and explain only non-obvious reasons. Nothing a consumer imports or renders changes. (#9524)
- Source comments in BottomSheet and BottomSheetSwitcher are shorter and explain only non-obvious reasons. Nothing a consumer imports or renders changes. (#9523)
- Component specs are no longer shipped inside the npm package; they live in the repo at
docs/specs/components/, one folder per component, beside each platform's spec.astryx swizzleno longer copies the component's spec file into your project. Nothing a consumer imports or renders changes. (#9007) - FileInput's
statusVariantdocs say that dropzone mode does not supportattached; usedetachedortooltipthere. Rendering is unchanged in this release. From the next minor release, a dropzone resolvesattachedtodetachedand defaults to it. (#9258) - The gesture arena's and the gesture host's internal doc comments sit on the declarations they describe. (#9114)
- Grid's
alignandjustifydocs no longer claim a'stretch'default. Unset, they leave the browser default,normal, which stretches items that have no natural size or aspect ratio. Rendering is unchanged. (#9347) - GridSpan: document the
xstyle,className,style, andrefprops, including that a setcolumnsorrowsreplaces the same grid placement instyle. (#9312) - Heading: document the
xstyle,className,style, andrefprops, including that amaxLinesabove 1 replaces anyWebkitLineClamppassed instyle. (#9328) - More source comments in the core hooks are shorter and explain only non-obvious reasons. Nothing a consumer imports or renders changes. (#9520)
- Source comments in the core hooks are shorter and explain only non-obvious reasons. A few hook doc comments are reworded. Nothing a consumer imports or renders changes. (#9514)
- HoverCard: document the
xstyle,className,style, andisOpenprops in every doc language, say that a text trigger is wrapped for you and an element trigger needs no ref, and say thathasHoverIndicationapplies to text triggers only. (#9536) - HStack: say that items follow the writing direction (right to left in RTL), that an explicit
hAlignorvAlignwins over itsjustifyoralignalias, and document theclassName,style, andrefprops. (#9540) - Recorded the component contract updates completed in this release. Covered records: #8783, #8822, #8878, #9050, #9058, #9062, #9081, #9083, #9090, #9096, #9100, #9101, #9103, #9105, #9108, #9111, #9112, #9113, #9117, #9118, #9124, #9125, #9127, #9128, #9129, #9131, #9132, #9133, #9135, #9158, #9175.
- Stack, VStack, and StackItem: say that a horizontal stack follows the writing direction (right to left in RTL), and document the
className,style, andrefprops, plusxstyleon VStack and StackItem. (#9583) - More source comments in the core utilities are shorter and explain only non-obvious reasons. Nothing a consumer imports or renders changes. (#9527)
- Source comments in ten core utility files are shorter and explain only non-obvious reasons. Nothing a consumer imports or renders changes. (#9522)
Other Changes
- Internal: the touch presentations' animator rechecks a finished animation's end in frame callbacks, starting a frame before it and looking again while up to two frames remain, instead of only on timers that a loaded page can run a frame or two late, so the frame that reaches the curve's end drops the animation before it paints, unless the timer that starts those rechecks itself runs more than a frame late. The timers remain for a page that draws no frames. Not exported from the package entry point. (#9285)
- Internal: the touch presentations' animator keeps each animation's frame-callback recheck of its curve's end its own, so a recheck still waiting for a replaced animation no longer stands in for the next animation's, which then fell back to its timer. Not exported from the package entry point. (#9325)
- Internal: the touch presentations' animator starts a call from rest, made in a task, at the first frame after it when the browser has not yet told the page that start (Chromium reports a compositor's start a frame or more later), so a retarget or a rebase in that window continues from the value on screen instead of replaying the curve from its start. A call made in a frame callback, or one whose first frame comes after a block, keeps the browser's start. Not exported from the package entry point. (#9255)
- AppShell drops an unmount Effect that repeated the release main's ref already performs; main's overflow observation and keyboard delegation are still released on unmount. No behavior changes. (#9262)
- Internal: the gesture recognizers and the menu press model share one guard for the browser's click after a gesture that already acted, swallowing it for 400ms or until the next press. Keyboard and assistive-technology clicks (
detail0) always pass. (#8360) - Internal: the touch motion tables register the three context-menu springs spec:AST-094 FR4 names (
springs.contextMenuLift,springs.contextMenuDismissandsprings.contextMenuMorph, a new row at response 0.3 s and damping ratio 0.8) as internal motion roles, so the registered roles are FR4's again. Nothing public changes: themes do not set motion roles, and no shipped component reads these springs yet. (#9432) - FileInput's source is formatted with the repository's Prettier settings. No behavior changes. (#9263)
- Internal: a gesture that cancels itself on a finger's move (a long press dragged past its tolerance) keeps that finger claimed until it lifts, so the page never takes the drag over midway; a resting finger is still given back when its gesture is cancelled. Not exported from the package entry point. (#8076)
- Internal: touch-action derivation, the native scroll probe and haptics for the gesture system. Not exported from the package entry point; no component uses them yet. (#8071)
- Internal: the gesture hooks call nothing back after unmount;
usePressTrackerbrakes with the host by default and keeps one tracker, so an option change or a new ref never drops a press in progress; the recognizer's arena plumbing isprotected. Not exported from the package entry point. (#8360) - Internal: gesture host fixes from review. A claimed pen holds only its own stylus touches, and a finger is matched to its scroller, its target and a moving element along the flat tree, through slots and shadow roots. Not exported from the package entry point. (#8360)
- Internal: the gesture host becomes the one document-level touch owner: the finger count, touch gates, and a kept press for continuous-tracking controls, whose element gets
touch-action: manipulation. A scroll lock's page hold and the finger-scroll watch keep their own listeners and ask the host only about the touches it owns. A second finger fails a one-finger pan that has not claimed, so the page can pinch. A scroll-edge pan holds a lone finger from the first move that pulls away from an edge every scroller under it is at, so those moves are cancelled before it begins; with a second finger anywhere on the screen the page keeps its pinch. A press tracker whose hold acts (a stepper's hold-repeat) can bring a selection lock for its presses, as a recognizer can. Internal, for the touch components that adopt them; not exported from the package entry point. (#8360) - Internal: the gesture system's DOM host (claims, click suppression, the browser's takeover, the pointer behind a contact), serving a mouse, a pen and a finger alike, with no page listener while idle where the primary pointer is fine. Not exported from the package entry point; no component uses it yet. (#8071)
- Internal: UIControl press tracking with control and cell profiles and the gesture hooks. Not exported from the package entry point. (#8076)
- Internal: the gesture system's README for component authors, with its browser proof in Chromium and WebKit. (#8076)
- Internal: gesture recognizer and arena fixes from review; a pan claims nothing before it begins at 10 pt; one velocity tracker for every gesture (
spec:AST-100: UIKit's measured blend, a scrolling surface's release through the pan'sscrollVelocity(), and FR2's release rules). Not exported from the package entry point. (#8360) - Internal: swipe, pinch and screen-edge pan gesture recognizers. Not exported from the package entry point; no component uses them yet. (#8061)
- Internal: a recognizer created with
claimsTouches: falseis a watcher: passive listeners only, simultaneous with every recognizer, and it follows a touch the browser takes for a scroll to the lift. Not exported from the package entry point. (#8360) - Internal: with the gesture host serving every pointer, a press tracker takes a mouse press as a press, painting at once with no scroll brake (AST-094 FR11); a finger's or a pen's hold that does something keeps text unselected under any primary pointer, a touchscreen laptop's included, while a mouse keeps its released behavior (FR41); a finger is read once where the browser sends Touch Events without exposing
ontouchstart; andperEventPointer, from before FR43, is accepted and does nothing. Not exported from the package entry point. (#8360) - Internal: the gesture recognizers hear page-wide input through the same shared stream on the window's capture phase, so an app's window-capture
stopPropagation, or a document-capturestopImmediatePropagationregistered before Core, no longer hides a touch from them; a recognizer that must claim a touch mid-gesture still needs the touch to reach its element. Each event type's listener is passive unless a subscriber cancels it (the gesture host'stouchendandcontextmenuwhile a claiming recognizer or press tracker is attached, the page hold'stouchmovewhile it holds, and the click guard'sclickwhile it is armed, and from the menu press model's first arm on), so a page of pressables registers no listener that can hold a scroll. (#8360) - Internal: ChatLayout drops a scrollbar style rule whose condition nothing ever set, and Popover, Table and the press feedback controller each read an internal marker through one shared name instead of a second hand-typed copy. No visible or behavioral change. (#9256)
- Item, Token and ChatComposer no longer run their own check for presses inside an open Tooltip or HoverCard; the layer root already keeps those presses from them. No behavior changes. (#9531)
- Internal:
useLongPresstakes its default duration and tolerance, 500ms and 10px on either axis, from the same source as the long-press gesture recognizer, so ContextMenu's long press behaves as before. A finger held on a DropdownMenu trigger passes its own 13px allowance instead (see the trigger drift fix). (#8360) - A bottom-sheet DropdownMenu's internal sheet preload reports a failed load in its result, with the loader's error, instead of catching it with an empty handler. Nothing changes for callers: a failed preload still raises no unhandled rejection, and the next open loads the sheet's actions. (#9069)
- Restore a Tall BottomSheet's internal position after keyboard dismissal. (#8742)
- Internal: the announcement routing inside open modals watches each dialog's
open,inertandaria-hiddenthrough Core's shared MutationObserver, so any number of open modals use one observer instead of one each. Routing is unchanged. (#9151) - The date picker's month scroller attaches and removes its four input listeners directly, each with one shared options object, instead of looping over an array of event names and creating an options object on every attach. Behavior is unchanged. The scroller and its listeners come from @vjeux's month scroller fix. (#9146)
- Internal: the motion roles test's header and the motion README's files table name the internal motion roles, exactly the ones
spec:AST-094FR4 lists. Documentation only; no behavior change. (#8502) - MultiSelector's source is formatted with the repository's Prettier settings. No behavior changes. (#9247)
- Internal: when Tab moves focus into a NumberInput with
formatValue, the focus handler itself puts the editable text in the input and selects it, instead of a layout effect that waited for the next render. Behavior is unchanged: typing still replaces the whole number. (#9150) - An internal
usePresentation/readPresentationresolves a component'spresentationprop into the surface to render and whether its touch input modes apply, keeping an omitted value distinct from an explicit'popover'so a caller's choice always wins over a touch default. Not exported from the package entry point. (#8298) - On iOS, a touch on an element the compositor animator is moving reaches what is drawn: the animator reports each moving element's offset from its layout box, and the gesture host sends the touch, press bounds and the tap's click there instead of to the layout position iOS WebKit hit-tests. (#8360)
- Internal: under Reduce Motion, a call that names the opacity a waiting dip returns to, with no travel, joins that dip instead of fading the element out a second time, and
reducedMotionFade()resolves the cross-fade's curve as a registered motion role where it plays. Not exported from the package entry point. (#8076) useResizable's size parsing, bound resolution, clamping and snapping, saved-size storage and content-box measurement move unchanged into one internal module, so the factory that follows resolves, clamps, snaps and saves exactly as the hook does. No behavior changes. (#9197)Tokenizerhands focus between its controls from callback refs and the Clear all confirmation's close handler, not from effects, asarchitecture:react-component-runtimeINV2 and INV6 require. Where focus lands is unchanged. The presentation swap and the sheet are internal (not yet public). Thanks @imdreamrunner (#7977). (#9162)- Internal: the gesture host applies a recognizer's own
selectionLockto that recognizer's contact and imports no lock itself; a long press brings one only when it has a hold (aminimumPressDurationabove 0), andselectionLock: nullopts out. Not exported from the package entry point. (#8360) - Internal: core's touch style keys stay literal, and a test pins every one to the touch presentation resolver's constants (
touchKeys, internal to core). An importeddefineConstskey compiles to a different StyleX priority than the same literal. No public export and no style changes. (#8331) - Internal: the touch presentations' animator drives a pseudo-element such as a dialog's ::backdrop: a static filling animation holds its value after a curve ends and after
set, a custom property on its host promotes it, and a Reduce Motion dip borrows and hands back the pseudo-element's own opacity. Not exported from the package entry point. (#8522) - Internal: the gesture hooks' attach-and-release lifecycle,
useAttachment, moves tohooks/(not exported), where other hooks can use it, anduseFingerScrollkeeps its finger-scroll watch through it instead of its own copy of that lifecycle. The gesture-sync helpers stay ingestures/gestureSync.ts. No behavior changes. (#9414) - Internal:
useFingerScroll(scroller)tells a finger's scroll from the program's, and the gestures README gains a guide to migrating a raw-touch drag onto the recognizers. Internal to the touch components: not exported from the package entry point or the gestures barrel. (#8360)
Contributors
Thanks to everyone who contributed to this release:
0.7.5
New Features
- Status colors are readable everywhere they appear, and Info is a status of its own. Each status (info, success, warning, error) now has a strong fill (
--color-<status>) with content on it (--color-on-<status>, at least 4.5:1), a pale fill (--color-<status>-muted) with its content (--color-on-<status>-muted), and readable text for the page and cards (--color-text-<status>). Status icons (--color-icon-<status>) and borders (--color-border-<status>) default to the readable text color. The Info roles (--color-info,--color-on-info,--color-info-muted, …) are new and no longer borrow your accent color.--color-success,--color-warning, and--color-errorandbg-<status>keep their meaning as the strong fills. In Tailwind,bg-info,bg-info-muted,text-on-<status>,text-on-<status>-muted, andtext-status-<status>are new;text-,decoration-,placeholder-, andcaret-<status>now use the readable text shade, andborder-,divide-,outline-, andring-<status>use the border shade, whilebg-,accent-,fill-,stroke-<status>, shadows, and gradients keep the strong fill. For example, Core's lighttext-warningis now[#753](https://github.com/meta/astryx/pull/753)F07instead of#E9AF08. To keep the fill color on text, writetext-[var(--color-warning)].What changes on screen:- Core's dark Error content (
--color-on-error) is now[#0](https://github.com/meta/astryx/pull/0)A1317instead of white, so text on dark-mode error fills reaches 4.5:1. Core's Info Badge uses[#0064](https://github.com/meta/astryx/pull/0064)E0instead of the accent ([#2694](https://github.com/meta/astryx/pull/2694)FEin dark mode). - Status icons (Icon
color="info|success|warning|error"), Stepper status glyphs, and Chat tool-call status icons use the readable shades. Core's light success icon is now[#09441](https://github.com/meta/astryx/pull/09441)Finstead of[#0](https://github.com/meta/astryx/pull/0)D8626. - Input and FileInput status borders use the border shades. Core's light warning border is now
[#753](https://github.com/meta/astryx/pull/753)F07instead of#E9AF08, and Butter's light success and warning input borders reach 3:1. - Banner draws its title, description, icon, and controls in the on-muted colors, and fills Info with
--color-info-muted. - Status fills keep a visible edge in forced-colors mode.
- Content on Chocolate and Matcha success and error fills, and on Stone success, warning, and error fills, now reaches 4.5:1.
- Every first-party theme sets a blue Info. Chocolate and Matcha Info Badges move from the accent to that blue; Butter keeps its own Info Badge colors.
- Neutral's
--color-success,--color-warning, and--color-errorare now the fills its Badges already showed, and its--color-infois[#0074](https://github.com/meta/astryx/pull/0074)E2([#6](https://github.com/meta/astryx/pull/6)D9CFEin dark mode). Its Badges, StatusDots, progress fills, and Stepper badges look the same; its accent ProgressBar, StatusDot, and Stepper now use Neutral's accent instead of blue. - Neutral no longer defines its undocumented local status tokens. Use the standard roles instead:
--astryx-theme-neutral-color-status-fill-success,-status-fill-warning, and-status-fill-error→--color-success,--color-warning,--color-error;-status-muted-accent→--color-info-muted;-on-tint-neutral→--color-neutral; the-on-tint-overlay-*and-destructive-overlay-*tokens →--color-overlay-hoverand--color-overlay-pressed.--astryx-theme-neutral-color-status-fill-accentkeeps its value but is deprecated.
Custom themes get the content and text roles they don't set: they are derived from the theme's status fills. To keep a component's previous color, set the matching role, for example--color-icon-successto your old--color-success. - Core's dark Error content (
- BottomSheets stack in the order they open. A modal sheet opened over another now sits on top of it: the sheet underneath keeps its state, moves back slightly, and can't be used until it is on top again; only one backdrop dims the page; and Escape, a backdrop tap, a swipe, or the system close gesture closes only the top sheet. Closing the top sheet returns focus to the sheet below, and closing a whole stack returns focus once, to where the flow started. A sheet inside another sheet's content now closes with it. Non-modal sheets (
hasScrim={false}) never stack. No props change, and a single sheet behaves as before. - Multi-step sheet flows no longer need a wrapper. When the top BottomSheet closes and another opens in the same update, for example from one state value that names the open step, the new sheet replaces the old one: it rises into place, the backdrop stays steady, focus moves into the new sheet, and closing the flow later returns focus to whatever opened it. This happens when the step change comes from inside the closing sheet, such as its own Continue or Back button. Non-modal sheets (
hasScrim={false}) replace each other the same way, and now open above all page content in the browser's top layer instead of relying on az-index. BottomSheetSwitcherand BottomSheet'ssheetIdprop are deprecated and keep working until a future minor release. Write each step as its ownBottomSheetinstead:- Replace
activeSheet/onActiveSheetChangewith onestepstate value. - On each step, replace
sheetId="id"withisOpen={step === 'id'}andonOpenChange={isOpen => !isOpen && setStep(current => (current === 'id' ? null : current))}. - Remove the
BottomSheetSwitcherwrapper and move itshasScrimonto every step. - Keep your step buttons as they are, for example
setStep('next').
To keep a step open, ignorefalsein itsonOpenChange(this replacesonCancel); to keep Escape but block the backdrop tap and swipe, usepurpose="form". A consumeraria-labelbecomes each step'slabel. Dialog-levelref,id,className, and styling props have no direct replacement: a standalone sheet'srefand props reach its panel. Flows that keep the switcher work as before, now with toasts above the flow and reduced-motion support.- Replace
- Popover takes
presentation, like DropdownMenu and Selector:'popover'(the default) anchors it to its trigger,'bottom-sheet'shows its content in a modal BottomSheet named bylabel, and'adaptive'uses the sheet on phones and the anchored popover elsewhere. In a sheet, positioning props such asplacementandwidthdon't apply, andxstyle,className, andstylestyle the sheet's panel. The sheet code loads only when it can be used. - Menus and selectors with
presentation="adaptive"(DropdownMenu, ContextMenu, MoreMenu, Selector, MultiSelector) and sub-menus that drill in on phones now switch to a bottom sheet by the shared phone-size rule on touch screens. A touch screen exactly 768px wide now keeps the anchored popover, and a phone in landscape (wider than 768px but shorter than 500px) now gets the sheet. A theme that moves itsmdbreakpoint moves this edge too. To keep a fixed presentation, passpresentation="popover"or"bottom-sheet", orpresentation="flyout"onDropdownMenuSubMenu. Desktop mouse and keyboard users see no change. @astryxdesign/core/themeexportscompactDefinition(widthBreakpoints?)andDEFAULT_COMPACT_DEFINITION: one shared rule for a phone-sized screen, narrower than the theme'smdbreakpoint (768px by default) or shorter than 500px, with ready-made media queries.CodeBlockhighlights C, C++, SQL, Rust, Kotlin, Swift, and Go with no setup, so you only ship the languages you use.Every other language is opt in, one at a time:- Import that language on its own and pass it as
language, for examplegraphqlfrom@astryxdesign/core/CodeBlock/languages/graphql. - Modules ship for
graphql,java,thrift,objectiveC(pathlanguages/objective-c),toml,powershell,ruby,lua, anddockerfile. - A string such as
language="graphql"still selects only a built-in language.
Your own languages work the same way.createCodeLanguage({name, identifiers, fileExtensions, fileNames, tokenize})makes a language from your own tokenize function.The built-in tokenizer stays within 4,608 bytes gzipped. Each module adds at most 512 bytes, and only when you import it.- Import that language on its own and pass it as
CodeBlocktakesendContentfor your own controls, such as a "Run in terminal" button. They sit just before Copy, in the header when there is one, otherwise beside the code, never over it. For a one-line command, leave out the title and passhasLanguageLabel={false}to get a single row with its controls beside it.- CodeBlock's
tokenizerprop is deprecated in favor of a custom language: passlanguage={createCodeLanguage({name, identifiers, tokenize})}with the same function. The prop still works.astryx upgraderewrites it when the block has a fixedlanguage, and leaves a TODO comment where it can't safely rewrite it. MarkdowntakescodeLanguages, a list of CodeBlock languages, so fenced code in Markdown can use the extra or custom languages too. A listed language wins over a built-in language of the same name, anddiff-<name>fences get diff coloring on top.- Expanding and collapsing can glide instead of jump. Create a handle with
useAnimatedLayout({containerRef})and pass it to Collapsible or TreeList asanimatedLayout: when one opens or closes, the content around it inside that container glides to its new place, revealed content fades in, and the chevron turns, all as one motion. Fixed and sticky elements stay put and the container never scrolls. Under Reduce Motion the change cross-fades on touch and is immediate with a mouse. Without the prop, nothing changes. - Table:
useTableRowExpansionaccepts the sameanimatedLayouthandle, so opening or closing a row's panel glides the rows after it, dividers included, instead of jumping. Under Reduce Motion rows fade on touch and change at once with a mouse; tables with column lines change at once. - TreeList chevrons and guide lines sit 4px closer to the start of the row, and the gap between chevron and label widens from 4px to 8px. Labels stay where they were.
Icontakes an optionalvariantto ask the active theme for alternate artwork, for example<Icon icon="info" variant="filled" />. The theme's icon receives the variant only when the theme lists it iniconVariants; otherwise it draws its normal artwork. Icons you pass as components never receivevariant, and it is never written to the page. Icons withoutvariantrender as before.- A theme icon can now pick its artwork by size: an entry in
defineTheme({icons})orregisterIcons()can be a function of{size, variant}, andIconcalls it with the size it renders at. Returningnulldraws no icon.getIcon,getExtendedIcon,getIconRegistry,useIcon, and a theme'siconsfield still return nodes, reading a function at{size: 'md'}. Existing icon entries are unchanged. - A theme can list the icon variants it supports, such as
filled, withdefineTheme({iconVariants}), and read them back fromtheme.iconVariants. Child themes inherit the list unless they set their own.@astryxdesign/core/IconexportsIconVariantMapandIconVariantfor typing variants. Themes withouticonVariantsare unchanged. astryx theme buildkeeps function icons and icon variant lists, so a built theme draws each icon at the same size and variant as the live theme, including icons inherited from another theme. A theme that listsiconVariantsgets matching types in<theme>.variants.d.ts. Themes without these features build exactly as before.- Themes can set the real size of each Icon size:
widthandheightinpxorremoncomponents.icon['size:sm'](orxsm,md,lg) now resize the glyph itself, for named icons and SVG components, in live and built themes. Before, they sized only the box around the icon. Sizes a theme does not style still render at 12, 16, 20, or 24px at a 16px root.astryx docs themegains an Icon sizes section. useCombobox(from@astryxdesign/core/Selector) can now build an accessible search-with-results on your own text field, such as a search box whose results replace part of the page, or an "add people" field in a dialog. SpreadgetFieldPropson your input,getListboxPropson your list, andgetOptionPropson each option. Focus stays in the field, arrow keys move through results, Enter picks, and Escape hides the list without closing a surrounding dialog. Announce result counts yourself withuseAnnounce. Existing uses behave as before.- Navigation menus support press-and-slide, as DropdownMenu does: in NavHeadingMenu, TopNavMenu, SideNavHeading's menu, TopNavHeading's product menu, BreadcrumbItem's menu, and TabMenu, a press that slides across the items picks the one it lifts on, with the highlight following the pointer. Link items are no longer draggable. Keyboard and screen-reader behavior is unchanged.
- On touch screens,
ScrollableAreashows the phone's own scroll indicator, which is easier to see than the faint bar it drew before. Mouse and trackpad scrollbars keep the neutral color. To keep the neutral color on touch screens too, setscrollbarColorthroughxstyle. - New
--ease-exitmotion token for things leaving the screen, beside--ease-standardfor things arriving. BottomSheet already closes on it, so nothing looks different, but a theme can now tune the exit.astryx docs motionand the theme template list it.
Fixes
- With an
animatedLayouthandle, content before a Collapsible or TreeList change now glides too when the layout moves it, for example items in a centered or end-aligned row. - With an
animatedLayouthandle, content after a change now glides even when it carries a resting transform, such as a Button or a swipeable row at rest, instead of jumping. - With an
animatedLayouthandle in a right-to-left container, content after a Collapsible or TreeList change now glides instead of jumping. - Screen readers now hear announcements made inside an open Dialog, modal BottomSheet, modal Drawer, Lightbox, MobileNav, or CommandPalette. Before,
useAnnouncemessages went to a page region the open dialog hid. Messages sent as a dialog closes are spoken once it has closed. Your code needs no change. Not yet covered: CommandPalette's result counts, Lightbox's position and zoom messages, and Selector's and MultiSelector's sheet messages. useAnnounce: messages announced at the same moment are now read together, in order, instead of the last one replacing the others, and an identical repeat is read once. A screen reader no longer misses a result count announced next to a confirmation.- A disabled ChatComposerInput keeps focus and its place in the tab order instead of sending focus to the page, and blocks editing and sending while keeping the draft.
- A disabled ComplexSelector ignores selections from a popup that was already open.
- Disabling an InputGroup now disables the inputs and Button addons inside it, unless a child sets its own state.
- A disabled Tokenizer blocks adding, creating, and removing tokens, and leaves its values out of form submission.
- Banner's status text color no longer leaks into your
endContent, including dialogs opened from it. - BottomSheet renders fewer page elements, with no visual change.
- With Reduce Motion on, BottomSheets (including
BottomSheetSwitchersteps) no longer slide or scale: on touch screens they fade in place within 200 ms, and with a mouse or keyboard they change at once. A swipe-to-dismiss fades out in place. - When a shorter BottomSheet replaces a taller one, the taller sheet moves down to meet it before fading, so the switch looks like one sheet changing height.
- Toasts shown from a
BottomSheetSwitcherstep appear above the flow and can be pressed. Before, the step covered them. - Toasts appear above an open BottomSheet and can be pressed. Before, the sheet covered them, and pressing a toast's action could dismiss the sheet instead.
- Typeahead and CommandPalette no longer announce "Loading" after the results have already arrived.
- ClickableCard, SelectableCard, and interactive Thumbnails show their pressed state under a finger in apps that compile Astryx from source (the Vite and PostCSS integrations, and Storybook). Mouse hover and press, and the precompiled stylesheet, are unchanged.
ChatComposer's status bar announces each error and warning once, without its decorative icon, and no longer announces a status that is already showing when the page loads.- Tapping the clear button of an unfocused TextInput or NumberInput now brings up the iPhone keyboard, without scrolling the page.
- In a CodeBlock with no title or language label, the Copy button no longer covers code. It sits in its own column beside the first line, so long lines stop before it, whether scrolled, wrapped, or right-to-left. Blocks with a header are unchanged.
- A long unbroken word, such as a URL or file path, in CommandPalette's empty message now wraps instead of spilling past both edges.
- ComplexSelector's trigger is now a combobox, so screen readers hear when the field is required. A custom
renderTriggercontrol gets the same role and states, and a disabled one keeps its tab stop without opening. Tests that find the trigger withgetByRole('button')should usegetByRole('combobox'). - ComplexSelector: your
aria-labeloraria-labelledbynow names the built-in trigger instead of being ignored. - A ContextMenu opened by a long press stays open when the finger lifts.
- With Reduce Motion on a touch screen, Dialog fades in within 200 ms instead of appearing abruptly. With a mouse it still appears at once.
DropdownMenuRadioItemnow runs youronClickandonPointerMovehandlers, after it selects its value. Disabled rows still select nothing and don't callonClick. Its docs now markvalueandlabelas required.- EmptyState announces reliably: it no longer uses
role="status", which screen readers read inconsistently. An EmptyState that appears or changes after the page loads announces its title and description once; one present at load announces nothing. Aroleyou pass now reaches it. Your code needs no change. - Clearing a FileInput returns focus to its visible button, so screen readers announce the field again.
- On touch screens, Tooltip and HoverCard open only on a real tap. Starting a scroll on an info icon no longer pops them open.
- Rows with
swipeActionsno longer block pinch-zoom, and a second finger hands the gesture to the browser. - With Reduce Motion on, tooltips, popovers, menus, and other layers opened by a finger fade in within 200 ms instead of appearing abruptly. With a mouse they still appear at once.
Layoutno longer uses a selector that could make the browser restyle the whole layout on every change, which slowed long documents. It looks the same.- Lightbox fills the visible screen, so Safari's toolbar on iPhone no longer covers the caption.
- A Lightbox opened before its first item arrives now opens when the item does.
- In right-to-left pages, Lightbox's arrow keys now match its Next and Previous buttons.
- Multi-digit numbers in List and Markdown stay on one line in a shared number column, so text and nested lists stay aligned. Bullet lists keep their spacing.
- Numbered List and Markdown markers end on the same edge with even-width digits, so every period lines up.
- Pasted-text counts, spoken shortcut names, Ctrl and Esc key caps, and file-size limits are now translated and use local number formats.
- DropdownMenu and ContextMenu rows under the mouse no longer show a keyboard focus ring after a click.
- DropdownMenu, MoreMenu, and ContextMenu shown as bottom sheets no longer keep the sheet and every item on the page while closed.
MobileNavis never wider than 85% of the screen, as documented, so even a 320px phone keeps a strip of page to tap to close it.- MultiSelector keeps your
aria-labelledby, read after the field's label. - A disabled
NavHeadingMenuItemwithhrefno longer navigates when clicked or activated. - Sliding the mouse across NavHeadingMenu or TabMenu items no longer selects their text.
- NumberInput keeps your
aria-labelledby, read after the field's label. - A disabled NumberInput stays in the tab order, so keyboard and screen-reader users can reach it and hear that it is unavailable. It is read-only and marked
aria-disabled="true"instead of using the nativedisabledattribute. Part of #7814. Overlay,DropdownMenuGroup, andMobileNavTogglepassid,data-*,aria-*, and event handlers through to the page, so test ids and analytics attributes work on them.- Pressing Escape right after opening a Popover or a collapsed SideNav submenu leaves focus on the trigger instead of moving it into hidden content.
- An open Popover no longer captures Tab presses made elsewhere on the page. Tab inside the popover still cycles, and Escape still closes it.
- A Popover rendered into an iframe or a picture-in-picture window now focuses, keeps Tab inside, closes on Escape, and returns focus as it does on the page.
- PowerSearch no longer announces its starting result count when it mounts in React StrictMode.
- On phones and tablets, presses made with a mouse, trackpad, or the Space key now show the pressed state.
- Type declarations resolve in projects that use
moduleResolution: NodeNext. RadioListno longer makes large pages restyle every row's contents on each change. It looks and behaves the same.- Scrollable areas (
ScrollableArea, and Table, CodeBlock, BottomSheet, and Schedule viewports) join the tab order as soon as their content overflows, including content that loads already overflowing. - SegmentedControl keeps your
aria-describedby, read before the disabled reason. - Selector keeps your
aria-labelledby, read after the field's label. - Selector's phone sheet no longer points screen readers at an option that hasn't appeared yet.
- A collapsed SideNav item's tooltip now belongs to the link or button itself, so keyboard focus shows the label and screen readers read it.
- SideNavHeading:
headerEndContentnow sits beside the heading link instead of inside it, so pressing a button there no longer also follows the link. - SideNav's rail collapses and expands smoothly instead of snapping, and the page content inside AppShell moves with it. Under Reduce Motion it cross-fades on touch and changes at once otherwise.
- Skeleton keeps pulsing in Safari while the page runs JavaScript. It looks and times the same.
- Slider keeps your
aria-labelledby, read after its label. - An idle Slider no longer keeps a page-wide listener running.
- A Slider drag belongs to the finger that started it: a second finger can't take it over or end it, and two fingers can still drag two sliders at once.
- A clickable Step reads as "1 Account" instead of "1Account". Nothing changes on screen. Fixes #7966.
- A Switch with long content in its row no longer makes the row restyle on every change. Its focus ring looks the same; a link inside the label or description keeps its own focus ring.
- Tabs and TabMenu triggers no longer shrink below their labels on pages that reset
min-width; the tab strip scrolls instead. - Pinned Table columns keep their row dividers while the table scrolls sideways, including theme and custom border colors.
- A disabled TextInput or TextArea stays in the tab order, so keyboard and screen-reader users can reach it and hear that it is unavailable. It is read-only and marked
aria-disabled="true"instead of using the nativedisabledattribute. Part of #7814. - TextInput keeps your
aria-labelledby, read after the field's label. - Thumbnail's Open and Remove buttons stay in place, focusable and announced as disabled, while they can't act, so keyboard focus no longer drops to the page.
- A toast dismissed while hidden, or before it first appeared, now really leaves the stack instead of taking an empty slot later.
- Tokenizer and PowerSearch put the text cursor right after the last token, on the last row.
- Tokenizer and PowerSearch tokens wrap before the clear-all button and loading indicator instead of running under them, and rows don't shift when a search starts or ends.
- A Tooltip that moved clear of its trigger stays clear when the trigger moves or the page scrolls.
- A Tooltip taller than the space above and below its trigger no longer covers the trigger: it opens beside it, or on the side with more room and scrolls.
- With Reduce Motion on, TopNav's mega menu fades on touch screens and opens at once with a mouse, instead of rising.
- Sliding the mouse across TopNavMenu action items no longer selects their text.
- Typeahead and Tokenizer hide an old "no results" row while the next search is running.
- Tapping a Typeahead's selected value to edit it, or the clear button in a Selector or MultiSelector search row, now brings up the phone keyboard on the first tap.
- In Typeahead, Tokenizer, and PowerSearch menus, an option is highlighted only when the pointer moves over it, not when it slides under a resting mouse, so Enter no longer picks an option you didn't point at.
VisuallyHiddencontent can no longer be made visible by accident:xstyle,className, andstyleno longer reach the element.Measured prop by prop againstmain's implementation, before and after this change:xstylearrived as the attribute only — thestyleattribute was unaffected — so passing it left a stray attribute on the page and changed nothing you could see.classNamenever reached the element, before or after.styledid reach the element, and an inline style could un-hide the content. It no longer does; this is the one visible change.
None of the three is styling surface onVisuallyHiddenProps:classNameandstylereach the element only through a cast or an untyped spread, andxstyleis documented as ignored, so typed code loses nothing.xstylestays declared onVisuallyHiddenProps, documented as ignored, so existing code keeps compiling.- Pinch-zoom works again over the TimeInput, DateTimeInput, and DateInput picker wheels.
Performance
- With an
animatedLayouthandle, a change in a long Collapsible or TreeList measures the page once instead of once per row. - Pages with many closed popovers, tooltips, and menus load faster.
- Closed Tooltips, Selectors, and ComplexSelectors render once when they mount, and Popovers and DropdownMenus render less.
- Scrolling a
ScrollableArea, Table, CodeBlock, or BottomSheet body does less work on each frame, so scrolling stays smooth on busy pages.
Documentation
- EmptyState now announces through the page's shared announcer regions. In tests,
getByRole('status')orgetByRole('alert')may match those regions; scope the query withwithin(container). - Badge's docs mark
labelas required, matching its types. DropdownMenuSubMenu's docs marklabelandchildrenas required, documentmenuDataTestId, and state thatpresentationdefaults to'adaptive'.ListItem's docs now say thatisSelectedmarks the row as the current item witharia-current="true".- Package links now point to the project's GitHub home,
meta/astryx. - SelectableCard's guidance no longer recommends it for single-choice groups, since each card is a checkbox.
- TabList's description no longer promises a built-in "more" menu (a narrow tab strip scrolls), and the library page template describes
MobileNavas the slide-out drawer it is.
Contributors
Thanks to everyone who contributed to this release:
0.7.4
New Features
BottomSheetSwitcherpresents each step in its own native<dialog>. Every childBottomSheetowns a dialog exactly like a standalone sheet; the switcher presents the selected sheet's dialog (showModal()with a scrim,show()without), keeps the previous sheet's dialog open and inert beneath the entering one through the handoff, and closes it once its panel has faded. One backdrop paints at a time: the retained dialog keeps the scrim until it closes, then the new dialog takes it over without a fade, so the page is never dimmed twice and the previous panel is never dimmed. Focus containment is the browser's own modal-dialog containment (as forDialog) instead of a script trap; the page scroll lock (the shared body lock, held once by the switcher for the whole modal flow, through a handoff and until after the exit), Escape and platform-close routing,purposedismissal rules, and focus return to the opener are unchanged. Going back to a sheet whose dialog is still fading closes and re-presents that dialog so the interactive sheet is the topmost layer again. (#7720) Public props, defaults, and exports are unchanged. Two observable details move with the structure: The switcher'srefresolves to the dialog hosting the flow — the active sheet's dialog, which changes on a handoff; the exiting sheet's through its exit; and, while the flow is closed, the dialog that hosted it last (or the first mounted sheet's) — instead of one persistent element; it is nevernullwhile a sheet is mounted, from the first commit on, and a callback ref's returned cleanup runs on each detach.onCanceland the forwarded dialog props apply to each sheet's dialog (arolegiven to the switcher included, except on arequiredstep, which is analertdialogas before), exceptidanddata-testid, which render once, on the dialog therefresolves to, from the first commit's synchronous re-render on; server markup of a flow that mounts closed carries them on no element (the shared dialog carried them). A non-modal flow orders its sheet dialogs inside a switcher-owned isolated wrapper that carries the one overlay value the shared dialog carried before.
Fixes
TextInput,TextArea,SelectorandMultiSelectorannounce "Loading" once, politely, through the shared announcement channel when they become busy, and the Spinner they show while busy is hidden from assistive technology. Before, the Spinner mounted as its ownrole="status"region already holding its name, which screen readers often skip, and it competed with the control's ownaria-busyas a second owner of the same feedback. A rerender or StrictMode replay does not repeat the announcement; settling and becoming busy again announces again. Tests that found the busy Spinner withgetByRole('status', {name: 'Loading'})should check the control'saria-busyinstead. (#7920)- Carousel: when the focused edge scroll button runs out (the carousel reached that edge), focus now moves to the scroll area without scrolling it, instead of to the opposite scroll button. No API changes. (#7926)
CheckboxInputannounces its busy start ("Loading") once, politely, through the shared announcement channel. The Spinner it shows in place of the check mark while busy sits inside the decorative, hidden indicator, so before this nothing told screen-reader users that the checkbox had become busy beyond itsaria-busy. Inside an open modal dialog the announcement goes to a status region in the dialog. (#7948)CommandPaletteItemnow reflects its highlighted, selected, and disabled states on thecommand-palette-itemtheme target asdata-highlighted="highlighted",data-selected="selected", anddata-disabled="disabled". A theme can now style the active keyboard result, the chosen value, or an unavailable command, for example.astryx-command-palette-item[data-selected]. States derived from CommandPalette are reflected too. Rendering, semantics, and props are unchanged. (#7967)CommandPaletteannounces each busy start ("Loading"), including its load on opening or clearing the query, once from a status region inside its dialog, and its search Spinner is hidden from assistive technology. Before, the Spinner mounted as its ownrole="status"region already named "Loading", and the palette's own "Loading" went to the page-level announcement channel, which an open native modal hides from assistive technology. Result-count announcements are unchanged. Tests that found the Spinner withgetByRole('status')should query the Spinner element instead. (#7956)- A busy
DateInput(isLoading, or a pendingchangeAction) no longer looks disabled. On the popover, native, and bottom-sheet surfaces the field keeps its ordinary paint and shows its Spinner while new commits are blocked; onlyisDisableddims the field. The busy field still takes no hover ring and keeps its keyboard focus ring. Props, semantics, and announcements are unchanged. (#7968) DateInput(popover, native and bottom-sheet presentations) andDateRangeInputannounce their busy start ("Loading") once, politely, through the shared announcement channel, and the Spinner they show while busy is hidden from assistive technology. Before, that Spinner mounted as its ownrole="status"region already named "Loading", which screen readers often skip, and it was a second owner beside the field'saria-busy. Inside an open modal dialog the announcement goes to a status region in the dialog. Tests that found the busy Spinner withgetByRole('status', {name: 'Loading'})should check the field'saria-busyinstead. (#7939)DateTimeInputandTimeInput(popover, native and bottom-sheet presentations) announce their busy start ("Loading") once, politely, through the shared announcement channel, and the Spinner they show while busy is hidden from assistive technology. Before, that Spinner mounted as its ownrole="status"region already named "Loading", which screen readers often skip, and it was a second owner beside the field'saria-busy. A change made inside the open bottom sheet under a pendingchangeActionis announced from inside the sheet. Tests that found the busy Spinner withgetByRole('status', {name: 'Loading'})should check the field'saria-busyinstead. (#7942)FileInputannounces its busy start ("Loading") once, politely, through the shared announcement channel, and the Spinner it shows while busy is hidden from assistive technology. Before, that Spinner mounted as its ownrole="status"region already named "Loading", which screen readers often skip. A file pick keeps its single "file selected" announcement, because it is one user action, even when it starts a busy period (changeAction, orisLoadingset fromonChange). Other busy starts, such asisLoadingon its own or a clear underchangeAction, announce "Loading". Inside an open modal dialog the announcement goes to a status region in the dialog. Tests that found the busy Spinner withgetByRole('status', {name: 'Loading'})should check the field'saria-busyinstead. (#7954)- Selector, DropdownMenu and ContextMenu: clicking an option inside a shadow root (open, closed or nested) selects it. The menus used to read the document's view of the click, which names the shadow host, so the click closed the menu without selecting anything. (#7914)
DropdownMenuSubMenu(withhasSpinner), an uploadingThumbnail, andChatMessageListwhile it loads older messages announce their busy start ("Loading") once, politely, through the shared announcement channel. The Spinner each one shows is hidden from assistive technology. Before, that Spinner mounted as its ownrole="status"region already named "Loading", which screen readers often skip; inChatMessageListit was also a second live role inside the log. Tests that found these Spinners withgetByRole('status', {name: 'Loading'})should query the Spinner element or the owner's busy state instead. (#7950)- ChatComposerInput: the trigger menu's loading row no longer mounts as a
role="status"region already holding its text, which screen readers could skip. The loading text is announced once per pending search through the shared polite channel instead, and a search that returns its results before the loading row is painted, such ascreateStaticSourceor a cached result, announces nothing; the visible row and itsloadingTextare unchanged. (#7900) Fixes #7859. - useTypeahead clears its pending buffer reset when its component unmounts or an
<Activity>boundary hides it, so a menu, list or selector removed within 750 ms of a typed character leaves no timer running behind it, and a hidden one comes back with an empty buffer (#7938) ComplexSelector,Typeahead,Tokenizerand a directly usedBaseTypeaheadannounce their busy start ("Loading") once, politely, through the shared announcement channel, and the Spinner they show while busy or while a search is in flight is no longer a live region: ComplexSelector's is hidden from assistive technology, and the search Spinner of Typeahead, Tokenizer and BaseTypeahead stays named as an image ("Loading") so the search's busy feedback keeps its name. Before, that Spinner mounted as its ownrole="status"region already named "Loading", which screen readers often skip, and it was a second owner beside the control'saria-busy. Inside an open modal dialog the announcement goes to a status region in the dialog. Tests that found the busy Spinner withgetByRole('status', {name: 'Loading'})should check the control'saria-busy, or find the search Spinner withgetByRole('img', {name: 'Loading'}). (#7930)
Documentation
BottomSheetSwitcheranatomy names its host partSheet dialogs— one native dialog per child sheet, the one hosting the active sheet carrying the flow's ref, id, modality, and dismissal — instead ofShared dialog. (#7720)
Contributors
Thanks to everyone who contributed to this release:
0.7.3
New Features
DropdownMenuSubMenutakesheaderandfooter, as the rootDropdownMenudoes, so a sub-menu can have a filter field above its rows, or an action such as "New folder" below them, outside the sub-menu's menu itself. With either, the sub-menu's surface (the flyout, or the drilled-in view on a phone) is a modal dialog named by its row: the row saysaria-haspopup="dialog", Tab and Shift+Tab walk the header, the rows and the footer and wrap, Escape returns to the row, and a pointer leaving the flyout closes it only once focus leaves too. AContextMenudoes not show a sub-menu'sheaderorfooter. Without them nothing changes.diff<DropdownMenuSubMenulabel="Move to"+ header={<TextInput label="Filter folders" isLabelHidden value={query} onChange={setQuery} />}+ footer={<Button label="New folder" onClick={createFolder} />}><DropdownMenuItem label="Folder A" onClick={() => move('a')} /></DropdownMenuSubMenu>
Fixes
TimeInput's arrow keys ignore a fractional increment instead of writing a malformed time such as "14:30.5":adjustTimereturns the time unchanged for a fractional minute delta (#7823).- Screen readers now announce a
Buttonthat is first rendered withisLoading(for example after a remount). Its visually hidden loading live region mounts empty and gets "Loading" on the next frame, because screen readers skip a live region that already holds its text when it appears. A Button that becomes loading after it mounts is unchanged, and a Button mounted idle does no extra render. ChatComposer: screen readers now announce a status message, errors assertively and warnings politely, once per occasion: a rerender does not repeat it, and a status that clears and then returns is announced again. Before, the status bar mounted as arole="alert"orrole="status"region already holding its text, which screen readers often skip. The message now goes through the shared announcement channel, and the visible bar no longer carries a live role. No API changes.ChatSystemMessage: a new chat notice inside aChatMessageListnow has one live region announcing it, the list's polite log, instead of also being a second live region nested in it (WCAG 2.2 SC 4.1.3). Its root no longer forcesrole="status", in either variant, so date and divider rows are no longer presented as status messages, and arolepassed to the component reaches its root. Tests that found a system message by thestatusrole should query it by its text instead.- Keyboard and screen-reader users can now reach disabled
CheckboxInput,CheckboxListitems,Switch,SliderandFileInput, and hear that they are disabled. Before, they rendered the nativedisabledattribute unless adisabledMessagewas set, so Tab skipped them. Now every disabled control exposesaria-disabled="true"and keeps the Tab stop it has when enabled, while toggling, selecting, dragging, opening the file picker and anyonClickstay blocked, and its value is still left out of form submission. A focused disabled checkbox, switch, slider thumb or file input shows its keyboard focus indicator. No API changes. - The agent guide that global mode writes to the home folder now tells agents to deliver a page built with Astryx, not only how to find things. Before, agents that found the right template could still build the page with a tool that cannot install packages and deliver a page with no Astryx in it. The guide now tells agents to work in a project folder (creating one if there is none); add
@astryxdesign/coreand@astryxdesign/clito a new project or one without Core, or, in a project that already has@astryxdesign/core, the CLI at the same version; runastryx initthere; follow the same template-first workflow and self-check the project agent docs give; and end by building the project and delivering that build. The guide stays version-free and names only commands every release keeps. The project agent docs are unchanged, and so is what@astryxdesign/core's install script prints: its copy of the shared agent-docs file only gains the same workflow lines. - Keyboard and screen-reader users can now reach a disabled
ComplexSelectorand hear that it is unavailable (WCAG 2.2 SC 2.1.1 and 4.1.2). Before, its trigger rendered the nativedisabledattribute, so Tab skipped it and a focused trigger lost focus when disabled; now it exposesaria-disabled="true", keeps focus, shows its keyboard focus outline, and still opens nothing. A press or key on it reaches no handler: not the toggle, not a caller'sonClickoronKeyDown, and not an ancestor's click handler. - Keyboard and screen-reader users can now reach a disabled
Calendarday orPaginationdot and hear that it is disabled. DisabledTreeListrows' expand toggle and action button, disabledPaginationdots and disabledCalendardays exposearia-disabled="true"instead of the nativedisabledattribute, while clicks, Enter and Space still do nothing and arrow keys still skip disabled days as before. No API changes. DateInput: keyboard and screen-reader users can now reach a disabled date field and hear that it is disabled. A disabled or busy field no longer renders nativedisabled: its input and calendar button keep their place in the focus order and exposearia-disabled, while typing and opening stay blocked, and a focused disabled field shows its focus ring. Tests that query a disabled DateInput withtoBeDisabled()or:disabledshould checkaria-disabled="true"instead.DateRangeInput: keyboard and screen-reader users can now reach a disabled field or preset and hear that it is disabled. A disabled or busy field and a disabled preset no longer render nativedisabled: the trigger, calendar button and presets keep their place in the focus order and exposearia-disabled, while opening and selecting stay blocked, and a focused disabled field shows its focus ring. Tests that query them withtoBeDisabled()or:disabledshould checkaria-disabled="true"instead (#7866).DateTimeInput: keyboard and screen-reader users can now reach a disabled or busy field and hear that it is disabled. It no longer renders nativedisabledon its text, native-picker or touch fields, or on its calendar and clock buttons: they keep their place in the focus order and exposearia-disabled, while typing, picking, opening and a caller'sonClickstay blocked, and a focused disabled field shows its focus ring.TimeInput's native picker button, which shares the time segment and stays out of the tab order, also moves fromdisabledtoaria-disabledand stays inert. Tests that query a disabled DateTimeInput withtoBeDisabled()or:disabledshould checkaria-disabled="true"instead.- Apps that use Core's prebuilt CSS without a StyleX build step now get the default data colors: the prebuilt CSS defines the canonical
dataVarsdefaults, so compiled imports and raw CSS references paint correctly. Dialog,BottomSheetandBottomSheetSwitcherstay open when a file picker inside them is dismissed. A file input fires a bubblingcancelevent when its picker closes without a choice, and all three took that event for a close request of their own and closed (a switcher closed its whole flow). They now act only on acancelaimed at their own<dialog>, so Escape and platform close requests (the Android back gesture) behave as before. No API changes.DropdownMenuRadioGroupnow forwardsref, and its docs explain controlled selection, how to name the group, when the menu closes, and how it composes inside aDropdownMenu.astryx initwrites the agent docs at the project root, in files the project commits, so Codex, Gemini CLI, Copilot CLI and Claude Code all read the block from the project root or any folder below it (#7497). It no longer writes agent docs into a project's subfolder, the home folder, or a settings folder in it such as~/.gemini.AGENTS.mdholds the block, created when missing. Before, a project with onlyCLAUDE.mdgot the block only there, so Codex and Gemini CLI never saw it.- Claude Code skips
AGENTS.mdin a folder that has aCLAUDE.mdor.claude/CLAUDE.md, so the Claude Code file the project already has keeps a full copy: rootCLAUDE.md, else.claude/CLAUDE.md. It keeps the copy even when it importsAGENTS.md, because Claude Code does not follow that import in a session started in a subfolder; started at the root, Claude Code then reads two. When both exist, the copy goes in rootCLAUDE.md, which projects commit even when they ignore.claude/, and a block in.claude/CLAUDE.mdis removed. Init creates no Claude file.astryx upgraderefreshes every copy, except in a project at the top of a home settings folder (see the next entry). - Gemini CLI reads only
GEMINI.md: init adds a one-line import,@./AGENTS.md, creatingGEMINI.mdwhen it is missing. It adds none whenGEMINI.mdalready importsAGENTS.md, inline or on its own line. It adds the import even when the project's.gemini/settings.jsonhas Gemini readAGENTS.mdthroughcontext.fileName: Gemini loads those settings only when it starts at the project root, so a session started in a subfolder would otherwise get no copy. Started at the root, Gemini then reads two. - The project root is the nearest folder at or above where init runs whose
package.jsondeclares an@astryxdesignpackage, else the nearest with anypackage.json. The search stops at a repository root and never counts the home folder. With nopackage.jsonfound, init writes where it runs, as before.docsWrittenstill lists each file relative to where init ran, for example../../AGENTS.md. - A
GEMINI.mdthat resolves outside the project, for example a link to a shared file, is skipped and reported indocsErrorwith one note (not an error line), in the default layout and in a project's own layout; the rest is written and init exits 0. - The managed block belongs to Astryx: init and
astryx upgradewrite, refresh, and remove only the block, whatever ignore rules or generated markers say, as 0.7.1 did, and never change the text around it. Every write stays inside the project: run in the folder 0.7.1 wrote, an agent file 0.7.1 wrote there whose path leaves the project still refuses the run with exit 1. The project's Claude Code file (rootCLAUDE.md, or.claude/CLAUDE.mdwhen there is no root one) that resolves outside the project and is a block-less import of an existingAGENTS.md, which 0.7.1 left alone, is skipped and reported indocsErrorwith one note, and init exits 0. Run from a folder below the project root, where 0.7.1 wrote in that folder instead, a project-root file whose path leaves the project is skipped and reported indocsErrorwith one note, the rest is written, and init exits 0. - While root
CLAUDE.mdis untracked and ignored by the repository's ignore rules (any ignore file from the repository root down, such as a monorepo's root.gitignore, the local exclude file, or configured excludes; init asks git, Sapling or Mercurial), a.claude/CLAUDE.mdthe project commits gets the copy too, so a fresh clone still gives Claude Code a copy;--agent claudeand--agent allwrite it there as well. A file the repository tracks counts as committed whatever the ignore rules say, as git and Mercurial ignore only untracked files, and when the repository cannot answer, the copy is kept, on the first run as on later ones. Such a copy that resolves outside the project refuses the run with exit 1 where 0.7.1 wrote it too; one 0.7.1 did not write (the one--agent claudeadds, or a block-less import of an existingAGENTS.md) is skipped and reported indocsErrorwith one note, and init exits 0. So is a.claude/CLAUDE.mdwhose block--agent claudewould remove beside aCLAUDE.md, since 0.7.1'sclaudepreset wrote onlyCLAUDE.mdthere. Beside a committed rootCLAUDE.md, with.claudelinked outside the project, three cases that 0.7.1 refused now exit 0 with nothing written: the default with a.claude/CLAUDE.mdof plain text, and--agent allwith one of plain text or a block-less import ofAGENTS.md; rootCLAUDE.mdholds the copy, so no write leaves the project. In a project that keeps its own layout, aGEMINI.mdthat imports no agent file now gets a copy, as the other agent files do. - The copy in
.claude/CLAUDE.mdis removed only once rootCLAUDE.mdholds the same block, and only the managed block between its markers: the rest of the file stays, and the file is deleted only when nothing but whitespace is left.astryx init --remove-agentsdeletes a file it created only when nothing but whitespace or init's own heading is left; 0.7.0 also deleted a file whose remaining text had a heading and any line with the word "guidance". astryx init --remove-agentsremoves the block at the project root, whereinitwrites it, and in the folder it runs in. Run from a subfolder, it removes whatinitwrote at the root, and a block an earlier version left in that subfolder; a root agent file with a block that resolves outside the project is left as it is with a note, and the run exits 0, as 0.7.1 did when it touched only the subfolder. Exit codes and the JSON shape are unchanged.--agent claudeand--agent allnever leave a block in bothCLAUDE.mdand.claude/CLAUDE.md, unless the project ignoresCLAUDE.md: whenCLAUDE.mdgets the block, a block in.claude/CLAUDE.mdis removed.--agent allkeeps theGEMINI.mdimport. The--agenthelp and the working-with-AI guide say so.--agent-docs-pathwrites where init runs, as before.astryx doctorfails when theGEMINI.mdimport points at anAGENTS.mdwith no block. The setup check in the CLI and in@astryxdesign/coreno longer counts that import as set up, and looks atGEMINI.md. The reminder to runinitthat commands print looks at the project root too, so it stops onceinithas run in a nested package.
astryx initandastryx upgradeno longer write agent docs into your home folder, or into a settings folder in it such as~/.geminior~/.claudeoutside a project. Agents read the files in those folders in every project, so a block there reached unrelated work. This follows the CLI's existing rules that no command writes agent docs into those folders and that a write outside a command's own folder is refused before anything is written.- Refused by
init: the home folder itself, and the top of any folder in it whose name starts with a dot (every such folder is a settings folder), even when it holds apackage.json. A folder below it with its ownpackage.jsonis a project and is set up normally, such as an agent worktree in~/.codex/worktrees/or~/.cursor/worktrees/, andastryx upgraderefreshes it. With--agent-docs-path, each file's own folder is checked: from the home folder,notes/AI.mdis written as before, whileAI.mdor.claude/CLAUDE.mdis refused. - What
initdoes instead: it writes no agent docs, reportsdocsErrorasinstall-failedwith the reason, and exits 0, as before. - Refused by
upgrade: refreshing a block in a project whose root is the home folder or the top of a settings folder, such as~/.dotfileswith apackage.json, with or without--apply. It leaves the block as it is, setsagentDocs.actiontoerror(neverwould-refresh), and warns with the folder and why; its other steps and its exit status are as before. With no block there, it gives the same reason instead of suggestingastryx init.astryx doctor's agent-docs fix does the same, and the setup reminder after each command stays quiet. - Migration: run
astryx initfrom the project's own folder, or add the block to the file by hand. Move a project rooted at the home folder or a settings folder into a folder of its own, or update or remove its block by hand. To remove a block an earlier version wrote into~/.claude/CLAUDE.md, runastryx init --remove-agentsin the home folder.
- Refused by
- Keyboard and screen-reader users can now reach a disabled
MultiSelectorand hear that it is unavailable (WCAG 2.2 SC 2.1.1 and 4.1.2). Before, its trigger rendered the nativedisabledattribute andtabIndex={-1}, so Tab skipped it and a focused trigger lost focus when disabled; now it exposesaria-disabled="true", keeps focus, still opens nothing, and submits no form value. Like a natively disabled button, it runs no caller event handler other than focus and blur, and a press on it reaches no handler. A focused disabled trigger shows a keyboard focus ring, dimmed with the rest of the control (WCAG 2.2 SC 2.4.7). - Keyboard and screen-reader users can now reach a disabled
LinkorClickableCard, and the buttons of a disabledToken. Before, they rendered the nativedisabledattribute ortabIndex={-1}, so Tab skipped them. Now each disabled control exposesaria-disabled="true"and keeps the Tab stop it has when enabled, while activation by click, Enter or Space,onClick, removal and navigation stay blocked; a disabled Link keeps no live destination and is exposed with the link role. APopoverno longer opens from a wrapped oranchorReftrigger markedaria-disabled="true"(for example a disabledButtonwith atooltip), including for a click dispatched straight on the trigger; before, such a click opened it. No API changes. - Keyboard and screen-reader users can now reach a disabled
Selectorand hear that it is unavailable (WCAG 2.2 SC 2.1.1 and 4.1.2). Before, its trigger rendered the nativedisabledattribute andtabIndex={-1}, so Tab skipped it and a focused trigger lost focus when disabled; now it exposesaria-disabled="true", keeps focus, still opens nothing, and submits no form value. Like a natively disabled button, it runs no caller event handler other than focus and blur, and a press on it reaches no handler. A focused disabled trigger shows a keyboard focus ring, dimmed with the rest of the control (WCAG 2.2 SC 2.4.7). Selectoroptions in a narrow list now shrink and truncate a long label with an ellipsis instead of being clipped past the list edge.Switch: a busy switch announces "Loading" once per busy start. Under React StrictMode the announcement used to be made twice.TimeInput: keyboard and screen-reader users can now reach a disabled field, or a busy bottom-sheet field, and hear that it is disabled. It no longer renders nativedisabledon its typed, native-picker or touch input or its picker button: they keep their place in the focus order and exposearia-disabled, while typing, arrow-key adjustment, opening, submitting a surrounding form with Enter, and a caller'sonClickstay blocked, a draft typed before the field became disabled is dropped, and a focused disabled field shows its focus ring. Tests that query a disabled or busy TimeInput withtoBeDisabled()or:disabledshould checkaria-disabled="true"instead.- Pages that use
Timestampwith an absolute format (date,time,date_timeand the other fixed formats) now prerender in Next.js withcacheComponentsturned on, where they used to fail the build:Timestampno longer reads the current time while rendering on the server, and absolute formats never read the clock.relative,relative_shortandautoread the clock on the client only: a server render or static prerender shows the full date and time in UTC, labelled, and the client switches to the format's normal output right after hydration, so server and client markup now always match. Client-only rendering is unchanged. No API changes (#7883). Tooltip: moving the pointer straight from the trigger onto the tooltip in one step no longer hides it, so it stays open while hovered (WCAG 2.2 SC 1.4.13).- A
SideNavItemin a collapsedSideNavnow shows its tooltip on hover and getsaria-describedby, even when the item first appears inside an already-collapsedSideNav, the common case for saved collapse state. Before, only an item that collapsed after it appeared got a tooltip. Fixes #7692.ATooltipwith ananchorRefthat renders inside the very element the ref points at, asSideNavItemdoes, now attaches however it mounted. The effect now re-checks the anchor once the commit has finished attaching refs; event listeners and thearia-describedbymerge and restore are unchanged. TopNavon narrow screens: a longTopNavHeadingnow gives way (it truncates with an ellipsis, or wraps when the heading is a link) instead of pushing the end content and the menu toggle past the edge of the bar, and the mobile drawer's close button is back on screen.Typeahead: clearing the value while editing it now empties the input and reportsonChangeQuery(''), instead of leaving the old label in a field with no value. Fixes #7038.
Performance
- Pages with many code blocks, such as a long Markdown document, paint sooner on first load:
CodeBlockinserts its syntax-highlight rules before the first layout read instead of after it, which cut first paint by 16–19% in 100–500 KB test documents (#7875). The rules and the highlighted output are unchanged. - Pages that update around a long
Markdowndocument stay responsive: Markdown skips re-rendering its document when a parent re-renders without changing the text or any rendering prop, and a link handler passed as a new function on each render no longer forces that work. The rendered output is unchanged.
Documentation
- The
DropdownMenuItemdocs now explain when an item is an action or a destination, disabled items, and supporting content.
Contributors
Thanks to everyone who contributed to this release:
0.7.2
Experimental APIs
- Drawer's full-viewport mobile coverage ships as experimental:
experimental={{isFullWidthOnMobile: true}}fills the viewport below 640px instead of keeping the 56px page reveal. Anything inside Drawer'sexperimentalprop may change or be removed in a patch release; omitting it keeps the stable behavior.
New Components
- Promote
DrawerandDrawerHeaderfrom the canary-only Lab package to Core, imported from@astryxdesign/core/Draweror the package root. The stable package now ships the full-height side panel with modal and non-modal presentation, the shared dismissal stack, Dialog'spurposedismissal policy, aDrawerHeaderwhose close button appears when givenonOpenChange, and Dialog-style container padding (--spacing-4by default,paddingprop, or a theme'sdrawerpadding), plus Core documentation and runnable examples. Canary users importing from@astryxdesign/labswitch to@astryxdesign/core/Drawer.
New Features
- An integration can set the command its users run the CLI with: a new
cliCommandfield inastryx.integration.*, such ascliCommand: 'acme astryx'. In a project that loads that integration, every command the CLI prints starts with it instead of the package-manager prefix (npx astryx,pnpm exec astryx): next-step hints, errors, suggestions, Doctor fixes,--help, the setup reminder, the agent-docs block, and doc text. If two loaded integrations set different commands, neither is used, and the newcli-commandcheck inastryx doctorwarns. An invalidcliCommandis ignored with aninvalid_cli_commandwarning; the rest of the manifest still loads. Docs, including an integration's, are now written with bareastryx ...commands, andastryx docsprefixes them for the project when it prints them. JSON output keeps every command bare, as before. The install-time setup reminder from@astryxdesign/coreand@astryxdesign/clinames the command the project's package manager runs, instead of alwaysnpx @astryxdesign/cli. - Adds the
@astryx.diffViewer.*keys to theencatalog so the labDiffViewerreads its file-status badges, line counts, line-number button labels, per-line "Added"/"Removed" labels, and empty-state messages from the translation runtime. No existing string changes; locales without a translation fall back to English. Itemacceptsalign="first-line", which centers each start and end slot on the label's first line. A small status dot, radio, checkbox, or timestamp beside a wrapping label now stays level with the first line, wherecenterdrops it to the middle of the row andstartleaves it above the line. A slot taller than the first line moves the text down rather than leaving the row, and a one-line row with no description looks the same ascenter.ListItem,RadioListItem, andCheckboxListItemaccept the samealignand pass it to their row. Themes can style these rows through theitemtarget'salignaxis. The default stayscenter, so existing rows don't change.- i18n catalog: add the English messages used by the Lab CommentComposer for its input, image upload, inline quote, emoji action, cancel action, and retry affordance.
- i18n catalog: add the English messages used by the Lab CommentThread for replies, reactions, edit history, resolution, errors, comment actions, and the unsaved-draft warning it announces when a dismissal would discard a reply or edit.
- i18n catalog: add the English messages used by the Lab Comments panel for its region, empty/loading states, pagination, and posting errors.
- i18n catalog: add the English messages used by the Lab EmojiPicker so locale catalogs and provider overrides can replace its labels, search status, loading state, and group names.
List: addedgeto choose where each row's text, dividers, and hover and selection backgrounds sit.padded(default) keeps today's look.flushdrops the rows' side padding, so text and dividers start on the same line as the list header and a heading above, with no container needed.outsetkeeps backgrounds' room around the text while reaching into the padding of a Card, Section, or Dialog, so text lands on the heading's line.bleedreaches rows to the container's edges with square corners, like Table rows in a Card.edgeCompensation="inline"is deprecated in favor ofedge="outset"and keeps working; its rows' outer room is no longer cut off by the list's swipe clip. Runastryx upgradeto rename it.Pagination:variant="compact"shows first/last buttons around previous/next whenhasFirstLastistrueand the page count is known. Compact still omits them by default, and theinputvariant still shows them unlesshasFirstLastisfalse.reset.css: in Chromium, the dropdown marker of an<input>with alistsits in the middle of the field. Chromium sets the marker on the field's line-height, so above a line-height of 1 it sits low, and the reset makes every field inherit the page's 1.5: the marker sat 3.5px below the middle of a 40px field, and further down on taller lines. Date and time fields, whose calendar icon uses the same part, keep their icon where it was. To keep the old placement, addinput[list]::-webkit-calendar-picker-indicator { line-height: inherit; }after the reset.SideNavItem: nested items now span the full width of the nav list, like top-level items, so their hover and selected fill lines up with the rows above them. Before, a nested item started 24px in from the list edge. The indent now sits inside the row, one--spacing-6step per nesting level, so icons and labels stay exactly where they were. The indent area is now part of the nested row, so it shows hover feedback and clicking it activates the item. Content placed directly inside aSideNavItemthat is not itself aSideNavItemis no longer inset by the children group. There is no supported way to keep the old inset look.TabMenupasses host attributes and DOM event handlers to its trigger button. The trigger keeps its button semantics, tab stop, and menu disclosure attributes; a caller'sonClickruns after the menu toggle.- Tables draw a line on every cell edge, not only between rows, on both
Markdownand the RichText surfaces, and the grid closes at the table's rim. A reader following one row across never needed vertical lines, but someone editing a table has to aim at a cell and judge where a selection stops, and the empty 3×3 a toolbar insert produces was three horizontal rules with no sign it had three columns. The line is the same--color-borderalready used between rows, the rim merges with it into one rule rather than doubling at the edge, and both surfaces move together — the read and edit renderings match block for block, more closely than before. TreeList: nested rows now span the full width of the list, like root rows, so their hover and selected fill lines up with the rows above them. Before, a nested row started at its indent. The indent now sits inside the row, so chevrons, icons and labels stay exactly where they were. The indent area is now part of the row, so it shows hover feedback, and clicking it activates the row: clicking a folder's indent toggles the folder, and clicking a row whose only action is its link anywhere outside its label follows the link, as Enter already did: modifier keys are kept, so Cmd/Ctrl-click opens a new tab, and a middle-click opens one too. Controls in a row's start or end content keep their own clicks, including role-based ones such as arole="switch"element, which no longer also toggle the row or run itsonClick. Guide lines draw above the rows, so a hover or selected fill doesn't break them, and they let clicks pass through to the row underneath. The one exception is a row with keyboard focus: it draws above the guides so they never cut its focus ring, which means that if it is also filled (selected or hovered), its fill covers the guides at that row. Padding set on a row through thetree-list-itemtheme target or an item'sclassName,styleorxstylestill composes with the indent.--tree-list-indentstill retunes the indent step. There is no supported way to keep the old inset rows.
Fixes
- Allow MetadataList label width without an explicit position while preserving single- and multi-column label defaults (#6310)
- AppShell: defer hiding the mobile nav's Activity boundary until its close animation finishes (#5701)
AppShellmounts the mobile nav drawer inside aReact.Activityboundary that flipped tomode="hidden"in the same commit as the drawer closing. React'sActivityhides its subtree withdisplay: none !importantsynchronously and re-runs the cleanup of every effect inside it, which cut offMobileNav's own slide-out CSS transition and cancelled its delayeddialog.close()before either could run. The drawer still closed correctly (a safety-net effect force-closed the native dialog on that same cleanup), just with the close animation skipped entirely.AppShellnow holds theActivityboundary visible for a beat after the drawer closes, strictly longer thanMobileNav's own worst-case close delay, soMobileNav's normal close effect gets a real chance to run its transition and its own timeddialog.close()beforeActivityever hides the subtree.MobileNavalso keeps its dialog rendered from the commit that closes it until its delayedclose()has run, instead of relying on the dialog's discretedisplaytransition to do so. A browser that does not hold that transition (WebKit) dropped the dialog todisplay: noneat once while it was still an open modal, so for about 200ms nothing was visible and the page stayed inert. The slide-out itself is unchanged. AspectRatio'sfit="cover"andfit="contain"now fill the box on the documented Tailwind setups. The fit rules lived inreset.css, in theresetlayer, and the setup guides put Tailwind's preflight in a layer above it, so preflight'simg, video { height: auto }won and a fitted image kept its own aspect ratio. The fit sizing now ships with the component's own styles inastryx-base: above preflight, and below Tailwind's utilities, so a utility class on the child still wins.reset.cssno longer carries AspectRatio rules. Withfit="cover"orfit="contain", a direct child's own Astryx styles (an Astryx component's own size orobject-fit) no longer override the fill. To keep a child's own size, set it with an inline style, unlayered CSS or a rule in a later layer, or leavefitunset.- The static
AvatarGroupOverflowchip (noonClick) is exposed to assistive technology as an image named by its count label ("5 more"). Before, it was a span with anaria-labelbut no role, a name the generic role does not allow, so screen readers could skip the count. This meets WCAG 2.2 SC 4.1.2 Name, Role, Value. Nothing changes visually; the clickable chip stays a button, and arolepassed by the caller still wins. Button(andIconButton) no longer use the nativedisabledattribute while a busy state (isLoading, or a non-interruptibleclickActionin flight) is the only reason the button can't be clicked. A natively disabled element can't hold focus, so the browser moved focus to<body>the instant an action started and never restored it — the classic reason busy state should be visual-only. Busy now usesaria-disabled(button stays focusable) witharia-busyand the spinner, matching the documented "Disabled vs Busy" API convention and the behavior input components already follow.isDisabled(andisDisabledtogether with a busy state) is unchanged — that still uses nativedisabled.isInterruptibleis also unchanged.aria-disabled, unlike nativedisabled, still lets the button dispatch a click — the busy guard already calledpreventDefault()to block the button's own action, but a click on a busy button could still bubble to a wrapping ancestor's own click handler (a clickable row, card, or backdrop), which the previous native-disabledbehavior never allowed.handleClicknow also callsstopPropagation()in that guard, containing an unavailable click at the Button boundary the way a natively disabled control always did.Thehref-rendered anchor path had the same gap for keyboard activation: it only wiredonClickto the busy guard, notonKeyDown, so a consumer's ownonKeyDownstill received Enter/Space on a busy-only anchor Button while it was announcedaria-disabled. The anchor path now wires the samehandleKeyDownsuppression the button path already had, so Enter/Space are swallowed and every other key still reaches the consumer, on both render paths.ChatLayoutScrollButton: the scroll-to-bottom pill now gives up keyboard focus, and refuses new focus, as soon as it starts to hide. Previously focus stayed on the fading pill for about half a second, untilvisibility: hiddenapplied, so it could sit on a control that was fading out or already transparent (WCAG 2.2 SC 2.4.7 Focus Visible). (#7738)- Preserve caller-provided IDs on CheckboxInput and keep labels associated with the native input.
- CheckboxList keeps a caller's
aria-labelledby. The group always replaced it with its own label id, so the caller's ids never reached the accessible name. The group is now named by its label and then the caller's ids, the same order RadioList and TimeInput use. - The setup reminder, the swizzle StyleX note, and one doctor line say only what is true
CommandPaletteInput: the query field now draws the shared keyboard focus ring. Previously it suppressed the browser outline without replacing it, so keyboard users could not see which field held focus.- Source builds through Next.js's Babel no longer fail with
Unknown property: L(orZs,Letter) when the app sets no browserslist or targets a browser without Unicode property escapes.Avatar's initials and the Markdown parser's emphasis and heading-link rules now build their\p{…}regular expressions at runtime, asNumberInputalready does, so there is no literal for Babel to rewrite. Matching is unchanged. DrawerHeadernow renders numeric zerostartContentinside its start slot and preserves numeric zeroendContentwhen no close button is present.Drawernow slides from the correct logical edge whendir="rtl"is set directly on the drawer, matching inherited right-to-left regions.DropdownMenuDividernow forwards host attributes and DOM handlers (id,data-*,aria-*, event handlers) to its separator, as other DOM-owning components do. Before, it accepted onlyxstyle,className,styleandrefand dropped everything else, so a separator could not carry a test id or an accessible label. Itsrole="separator"and orientation stay component-owned.- DropdownMenu: load the touch bottom sheet only when a menu shows it
DropdownMenuimported its touch sheet (BottomSheet, its gestures, and the touch action list) up front, so every page with a dropdown shipped it, even when the menu only ever opens as an anchored popover. The sheet now loads on demand, the wayContextMenualready loads it. A popover-only dropdown's own code drops by about a third (about 23 KB gzipped). Bottom-sheet and adaptive menus behave as before. The sheet starts loading when the trigger mounts, and a menu opened from the keyboard before it arrives still focuses its first action once it loads. EmptyStateno longer leaves blank icon or action spacing when those optional slots receive a boolean or an empty string. An empty description also omits its theme target. The docs now describe configurable heading levels and map the container anatomy to the public theme target.- Keep
Field's horizontal-label layout marker authoritative when callers pass conflicting data attributes, and keep hidden descriptions visually hidden in that layout. Correct its custom label-icon type, all three status placements, complete anatomy, and guidance for controls that cannot safely use attached status. FieldStatus(and any element usinguseEntryAnimation) no longer causes a hydration mismatch on server-rendered pages. An element that arrives in the server's HTML now hydrates without the entry style and never plays its entry animation, even when hydration runs after the page has painted; elements mounted after hydration still animate.useEntryAnimationno longer documents server rendering as unsupported.- Keep
FormLayout's direction metadata authoritative when callers pass conflicting data attributes. GridSpankeeps its content inside the span. A child whose min-content width is wider than the span, such as aTokenizerwith a long token, used to stretch the span's column past the grid cell; it now gets the span's width and truncates the way it does outside a Grid (#7438)- Keep
Grid's theming metadata authoritative when callers pass conflicting data attributes. useHoverCard: closing a hover card withhide()or Escape while the pointer rests on the card no longer leaves the next open stuck. The hook kept believing the pointer was still over the card, because a card closed that way unmounts without amouseleave, so the trigger's next hover-open never closed on leave or afterhideDelay. Both paths now clear that state, as the touch dismissal already did.- Compute ISO week numbers (
Calendar hasWeekNumbers,getWeekNumber) on UTC anchors instead of local-timeDatearithmetic. In timezones whose DST ends after New Year (Sydney, Auckland, Santiago), the local-millisecond difference between the week's Thursday and January 1 carried the DST offset, and in years whose January 1 is a Friday that extra hour rounded a whole week up: the entire ISO week 14 of April 2021 displayed as week 15. Week numbers are now identical in every timezone. - Anchored layers (
Popover,DropdownMenu, and every component built on them) now keep their safe-area gutter and dynamic-viewport size cap in the shipped stylesheet. The compiled CSS referenced an undefined variable for the preferred value, so every browser used the fallback: on a phone with a dynamic toolbar or a notch, a tall layer could run past the visible screen or under a declared bottom bar. Desktop sizes are unchanged. createMarkdownFrontmatternow hands itsparsefunction a plain object, so a parser that returns the decoded fields unchanged (parse: fields => fields) is accepted as metadata. Before, the record had no prototype, failed the JSON-like metadata check, and the document fell back to readable text with its frontmatter still showing.MultiSelector: the row action cell the keyboard reaches with the inline-end arrow draws the standard focus ring. Before, its outline read four CSS variables that nothing declared, so no ring showed on the active action cell.- PowerSearch: clear every filter with one press of the clear-all button instead of removing only the last filter.
- Prevent pressing a built-in PowerSearch filter token with the mouse from opening search suggestions before the filter editor. Token editing, removal, and keyboard navigation retain their existing behavior.
- Keep built-in PowerSearch value controls disabled in read-only filter editors, matching custom editors.
- RadioList keeps a caller's
aria-labelledby. The radiogroup always replaced it with its own label id, so the caller's ids never reached the accessible name. The group is now named by its label and then the caller's ids, the same order TimeInput uses. - Restore focus to the element that opened a Dialog when its content mounts in the open commit. The opener was captured in the Dialog's passive effect, which runs after a freshly mounted DialogHeader's autofocus effect had already moved focus to the dialog's own title — closing then restored focus to that detached title and the user's focus landed on
<body>. The capture now runs in a layout effect, before any descendant's passive effect. (#5637) astryx searchfinds more of what a reader means when the words differ from the catalog's.astryx searchranks a match on more of your words above a shorter named entry.SideNavItemkeeps a caller'sclassNameon its row element (the link or button, and the collapsed rail item) next to its own classes. Before, the row's generated class replaced it, so a class passed to style the row (for example, a cursor while a row is dragged) never reached the DOM, even thoughstyle, ARIA, data attributes and handlers did.- Shrink Token's invisible remove-button target from 44px to 24px without changing the visible icon. Clicking adjacent text or values in PowerSearch now edits the filter instead of accidentally removing it.
- DropdownMenu submenu flyouts close with their menu when it is light-dismissed: previously a submenu opened by tap or a fast click stayed open (and re-anchored to the viewport corner) after the menu was dismissed and reopened. A hover-open scheduled on a submenu trigger before the menu closed from elsewhere is also cancelled, so it can no longer reopen a flyout behind the dismissed menu
Switchnow adds a caller'saria-describedbyto the switch control, ahead of its own description, status, and disabled-reason ids. Before, the value landed on the field wrapper, so a hint rendered elsewhere on the page could not describe the switch to assistive technology.Switchnow puts a caller'saria-labelledbyon the switch control. Before, the value landed on the field wrapper, so a visible title elsewhere in the row could not name the switch for assistive technology.- A truncated
TextorHeading(maxLines) now re-measures when its content changes, not only when its box resizes. A fixed-width single-line status whose message changed kept showing the first message in its truncation tooltip, and a new short message could keep a tooltip while a new long one lacked one.useTruncationnow also observes the element's text, so the tooltip text and the truncated state follow the current content. ToggleButtonkeeps toggling when it also receives anonClick, for example from a wrapper that renders it as its trigger. ThatonClickused to replace the toggle's own click handling, soonPressedChangenever ran and aToggleButtonGroupmember never asked its group to toggle (pressedChangeActionstill ran). The caller'sonClicknow runs first and the toggle request follows. On a standaloneToggleButton, callingpreventDefault()in thatonClickcancels the request: neitheronPressedChangenorpressedChangeActionruns.useTooltip(and every component built on it, such asButton'stooltipprop) now drops a show that is still waiting out its delay whenisEnabledturnsfalse. Before, hovering a trigger and then disabling its tooltip within the delay let the timer fire anyway: the tooltip opened after its triggers were turned off, with no pointer-leave listener left to close it. A pending hide still runs, and an enabled tooltip is unchanged.- Tooltip: an icon-only trigger now opens instead of throwing. The layer passed its trigger to
showPopoveras the invokersource, which the Popover API declares as anHTMLElement; a caller-rendered icon is anSVGElement, whose dictionary conversion throws before the popover opens, so the hint never appeared. An icon trigger now reachesshowPopoverwithout a source — positioning is unchanged, since the layer is anchored by its anchor-name pair, and only the invoker's focus order is given up. - A collapsed
TopNavMenuorTopNavMegaMenusection in the mobile drawer is nowinertand hidden from assistive technology, so Tab no longer moves focus onto links that are not shown and screen readers no longer list them under a section announced as collapsed. - An expanded
TopNavMenuorTopNavMegaMenusection in the mobile drawer no longer clips the focus ring of its items. The section still clips while collapsed and while it animates open or closed. Typeahead,Tokenizer, andPowerSearch: clear loading state and stop busy indicator when search source is replaced (#7457)
Performance
TextandHeadingwithmaxLinesandhasTruncateTooltip={false}no longer measure their text or observe it for resizes and content changes. Only the tooltip uses that measurement, so with the tooltip off the text is cut by CSS alone, and a long table of truncated cells no longer pays a layout read per cell. Rendering is unchanged; with the tooltip enabled (the default) nothing changes.
Documentation
AvatarandAvatarGroupdocs list the numeric sizessizeaccepts (16, 20, 24, 32, 36, 40, 48, 60, 64, 72, 96, 128, 144, 180) instead of implying any pixel value, and say that anAvatarGroup's size always overrides a childAvatar's size, including the group's default.- Docs and CLI examples import each Core export from the path
astryx component <Name>prints. ContextMenudocs now state that data-drivenitemsand compoundmenuContentare mutually exclusive choices instead of markingitemsas unconditionally required.- Document DropdownMenuGroup's complete wrapper props, group semantics, and non-interactive heading guidance.
- Document FieldLabel's complete public prop surface, group-label semantics, and supporting descriptions.
- Make
FormLayoutdocumentation match logical fractional grid tracks and viewport collapse, and make the public layout target discoverable from component anatomy. - Make
GridandGridSpandocumentation match fractional track sizing, responsive repeat behavior, implicit rows, and explicit-column spans. useCombobox, the single-select combobox hook exported from@astryxdesign/core/Selectorthat powersSelectorandCommandPalette, now has hook docs, soastryx hook useComboboxandastryx search comboboxreturn it with its options, its return fields, and how to wirearia-activedescendantwhile focus stays on the control.- The
useMultiComboboxhook docs now say that ArrowDown or ArrowUp opening the list lands on the first or last option even withhasSearchor a disabled end option, and that the hook still handles Home and End withhasSearch, so a search input that keeps those keys for the caret stops them first and relies on PageUp and PageDown. useMultiCombobox, the multi-select combobox hook exported from@astryxdesign/core/MultiSelectorthat powersMultiSelector, now has hook docs, soastryx hook useMultiComboboxandastryx search comboboxreturn it with its options, including the grid rows with an action cell, its return fields, and how to wirearia-activedescendantwhile focus stays on the control.- InternationalizationProvider documentation now names its nonvisual provider boundary so the new component contract can map its anatomy without implying rendered DOM. (#6048)
ListItem's docs now listlabelas aReactNode, matching its props type: a string is truncated to one line, and any other node renders as given. They used to saystring, which told readers a rich label had to be restructured away.
Other Changes
VStackandHStackcome from@astryxdesign/core/VStackand@astryxdesign/core/HStack,Headingfrom@astryxdesign/core/Heading,Textfrom@astryxdesign/core/Text, andThemeanddefineThemefrom@astryxdesign/core/theme.- This covers the guides, the
Carddocs, the next stepsastryx initprints, the install exampleastryx theme buildprints, the wiring exampletheme addprints, the build rules, the theme-module fixastryx doctorprints, and the annotated theme template. - Every path was already exported. Nothing else changes.
- The "run init to finish setup" reminder no longer prints where agents already have the Astryx prompt. In a git repository it looks for init's block in the agent docs from the project up to the repository root, because coding agents read every agent doc in between, so a package in a monorepo that ran
initat its root stays quiet. This holds for every command and for the reminder printed when@astryxdesign/coreor@astryxdesign/cliis installed. Running the CLI from its own source checkout, inside that checkout, prints no reminder. A project with no block in reach still gets it, and--jsonnever prints it. astryx swizzleno longer says StyleX components "render unstyled (no error)" without a StyleX compiler. Importing them throws StyleX's "Unexpected 'stylex.create' call at runtime" error and the page does not render, and the note now says so.- In an integration package, where the package's own manifest loads,
astryx doctor's implicit-integrations line no longer says that "every loaded integration is named in astryx.config". It names the package's own manifest: as the only loaded integration, or beside the integrations astryx.config names.Classification: contract-restoring. Only message text changes: JSON keys, check ids, statuses, and exit codes are unchanged. The doctor line's new text also appears in its--jsonmessage. - Internal groundwork for a sub-menu's header and footer:
DropdownMenu's Tab walk through its header, menu and footer moves, unchanged, into a module of its own, so another menu level with regions can share it.DropdownMenu's behavior does not change. - Adjacent query words that join into a component, hook, or template name, or into a one-word keyword, match it:
table header cell with sort arrowfindsTableHeaderCell,tree view foldersthetreeviewkeyword, and a hook answers to its words withoutuse. Most of a name, a name's leading words, or a run of its words also count for components and hooks, a step below the full name. - A query that is one camelCase identifier and matches nothing as typed is read as the words it spells, so an unknown API name such as
useTablePaginationStatereachesuseTablePagination. In a query of several words each identifier stays one term. - When the whole query is an entry's name, these readings add no near siblings beside it. A match on a joined keyword never ranks above an entry the query names, and a match on part of another name does only when it spans more query words than that entry's name.
- A gerund matches its verb (
spacingandspace,dragginganddrag), and a plural can start a longer word through its singular (tokensandTokenizer). - Core component docs declare more keywords: other libraries' names (
scrollarea,togglegroup,pageheader,splitpane,circularprogress,linearprogress,commandmenu,relativetime,sidesheet,descriptionlist,inlinecode) and common glyph names onIcon, since any icon library's glyph renders through it. - The JSON shape is unchanged.
- A match on part of a longer name that reads more of the query than the entry the query names is no longer held below it:
dropdown menu radio optionsleads withDropdownMenuRadioItem, notDropdownMenu. useResizabledrops thesplitviewkeyword, which put it ahead of the side-panels guide.
Contributors
Thanks to everyone who contributed to this release: