What's New
Release notes and changelog for all packages.0.7.17
Experimental APIs
- Adds two English catalog messages for the Lab media player's visible time readouts (elapsed and total, and remaining time), so a locale can translate them.
New Features
- AlertDialog: under a finger the alert appears and leaves the way an iOS alert does. It scales down into place from 1.2 while it and the dimming fade in, on the theme's entrance timing. When it closes it fades out with the dimming, on the theme's exit timing, and a close or a reopen midway turns back from where it is. While it appears a touch does nothing, and keys and assistive technology still act. While it leaves nothing reaches it, but a toast its action raised stays live and its words are read. With reduced motion it only cross-fades. On a phone (a compact window under a coarse pointer) the width with no
widthprop goes from 400 px to 320 px in every theme; awidthyou pass still wins. With a mouse nothing changes. - A Button whose label is cut short in a narrow row shows its full label in a tooltip when keyboard focus reaches it, and a ToggleButton's cut label now shows an ellipsis. Labels that fit look the same and show no tooltip, and screen readers hear the name once.
- Chat surfaces now default to the container radius:
--radius-chatdefaults tovar(--radius-container)instead of28px, a theme that sets--radius-containerbut not--radius-chatdeclares the alias at its root, and a radius scale no longer sets--radius-chat(it set the page step), so chat follows the theme's container, also where the theme sets its container over the scale. This changes the corners of ChatComposer, its drawer and status bar, and ChatMessageBubble, and the buttons inside the composer take their normal corners. The send button stays circular inside a composer, as it is outside one: a theme whose composer corner made the send button a rounded square (controls taller than 32px, or a chat corner under 28px) now draws a circle, unless it sets thechat-send-buttonradius. Butter, Chocolate, Gothic, Matcha, Neutral and Stone set--radius-chat: 28px, and Butter keeps its 16px send-button corner, so they look the same; Y2K sets--radius-chat: 0pxand stays square. A theme that extends one of them keeps that chat radius. To keep the 28px chat corners in another theme, add--radius-chat: 28pxto its tokens. Set the token in the theme rather than on an ancestor such as:root: a theme scope that declares it now replaces an inherited value. - Component docs:
playground.mobileholds the props of a second render at a phone viewport, merged overdefaults, for a component whose layout changes at phone width; the theme editor's part census renders it too. AppShell declares its mobile layout there (the menu button in the top bar, the open drawer); its playground defaults are unchanged. - Banner gives themes two more parts:
banner-message(the title and description together) andbanner-title. The default status icon no longer sits in an extra box, so a theme that hidesbanner-iconleaves no empty gap before the message. A theme can now draw a one-line alert with no icon; one space separates the title and the description in every banner, so the gap between them is the same on one line. The four built-in statuses look the same. A status with no default glyph and noiconloses the empty 8px space before its message. defineTheme({palette}): a theme can take its color tokens from a few seeds.themePalette({accent, neutral, success, warning, danger, info, vibrancy, recipe})from the new@astryxdesign/core/paletteentry generates the palette and maps it to the color tokens the CLI theme editor sets for the same color settings (surfaces, text, borders, icons, the accent and the status colors); explicittokensandcomponentsstill win, one by one. A palette that names no recipe runsastryx-oklch-v1. With aneutralseed, a pinned recipe keeps the generated shades across upgrades. Without one, the surfaces are Core's defaults, so shades picked by contrast against them follow the installed Core, as does secondary text lifted on a tinted part. Only apps that import@astryxdesign/core/paletteship the generator. The entry also exportsgenerateTonalPalette()and its types.- Text inside a
Themethat sets no line height of its own now uses the theme's body leading (--text-body-leading), as Core's own body text does, instead of the reset's 1.5. Plain text in a Card or Stack and a Blockquote's quote follow the theme's line height and move when a theme changes it. Core parts that set a text role's size now also set that role's leading, so none of them draws on an inherited line height (inlineCodekeeps the line of the text around it, and a few parts keep a fixed line height they are measured or aligned to: the Selector trigger, the Stepper step description and the chat composer): Table cells, header cells and row index numbers, Calendar month heading, day, weekday and week-number text, the touch date and time fields' titles, weekdays and wheels, Stepper step text, Pagination, Collapsible titles, Command Palette items, Dropdown and nav menu items, Selector and MultiSelector items and empty states, the MultiSelector trigger's overflow count, the PowerSearch nested editor's root label, the Typeahead empty state, the chat trigger menu's empty and loading states, the chat system message and pasted-text details, Code Block sizes, Empty State compact text, Segmented Control and Token small sizes, the Switch description, the top nav menu's item descriptions, the chevron in a breadcrumb item's menu trigger, the Avatar Group overflow count, the skip link, Tokenizer and Slider labels. With the default theme, 14px text moves from 21px to 20px lines; 12px text in these parts moves to 20px lines (the supporting leading), from 18px or about 17px; 12px text that only inherits moves from 18px to about 17px; 17px text such as Collapsible titles moves from 25.5px to 24px; the Avatar Group overflow count's line grows inside its fixed circle. Inherited text outside a Theme is unchanged; the listed parts take their role's leading wherever they render, also outside a Theme. To keep the old lines: for inherited text, set a line-height on your own container inside the Theme, or set--text-body-leadingin your theme (which also sets Core's own body text). The listed parts follow their role's leading token instead (--text-body-leading,--text-label-leading,--text-supporting-leading,--text-large-leadingor--text-code-leading): set that token in your theme, or style the part through its theming target. - LayoutContent names the container it sits in (
data-container="dialog","card"or"bottom-sheet"), as LayoutHeader and LayoutFooter do, so a theme can style a dialog's body apart from its header and footer throughlayout-contentwithcontainer:dialog, for a full-bleed title bar over a padded body and a footer bar. The Dialog's own LayoutContent takes it, an AlertDialog's body included. - MobileNav's painted drawer panel carries its own theme target,
mobile-nav-drawer, with the resolvedside, so a theme can give the panel a surface and text colors without painting the full-screen overlay behind it. The default look does not change. - Themes can draw Pagination's controls as one joined strip. The control row carries
pagination-list, each of its Button controls carriespagination-item(the current page's reflectsdata-selected), and the ellipsis carriespagination-ellipsis. On the cells,pagination-itemcompetes with the theme'sbuttonentries: its base rule loses to abuttonentry keyed on variant, size or elevation, and its hover and selected rules weigh the same as a one-keybuttonrule, so the later one in the theme wins. The default look does not change. - Themes can reach parts that painted with no target of their own. The default look does not change.
- Each key badge in Kbd carries
kbd-key. - The Typeahead result popup carries
typeahead-popup. - Calendar's range band and hover-preview band carry
calendar-rangeandcalendar-range-preview, withstartandendon the first and last day. - BottomSheet's grab bar carries
bottom-sheet-handle. - AlertDialog's title and description carry
alert-dialog-titleandalert-dialog-description, and a theme'sheadingandtextrules no longer reach them. A theme that styled them throughheadingortextkeeps that look by repeating those rules onalert-dialog-titleandalert-dialog-description. - LayoutHeader and LayoutFooter reflect
container(card,dialogorbottom-sheet), so a theme can style a dialog's header without a card's. - ToggleButton reflects
groupedinside a ToggleButtonGroup. - An accent Link's hover color reads
--link-hover-colorwhen a container or theme sets it.
- Each key badge in Kbd carries
- Themes can reach four more parts. The default look does not change.
- A theme's
spinnerindicator replaces the ring a Spinner turns. - A theme's
tree-disclosureindicator replaces a TreeList row's rotating chevron with a mark for each state. - NumberInput's stepper buttons carry
number-input-stepperwithdirection(incrementordecrement). - The close buttons of Toast and Banner carry
toast-closeandbanner-close, so a theme can style them apart from other buttons. Toast's close button draws in the toast's text color; Banner's keeps its status text color.
- A theme's
- TopNavHeading carries
data-mode="drawer"when TopNav draws it as the phone menu's title, as TopNavItem already does, so a theme keys the menu's title withmode:drawer(for example a heading colored for a dark top bar, kept readable on the menu's own surface). In the bar it carries nomode; nothing else changes. - A Markdown heading's copy-link button now shows when the clipboard write fails, as CodeBlock's copy button does: the
#becomes a cross for 1.5 seconds, and the button is named and announces "Failed to copy value to clipboard." It used to fail silently and leave#unchanged. The error itself is not shown. - On a phone or tablet, TextInput, TextArea and NumberInput keep themselves above the on-screen keyboard, with nothing to turn on. A field in a page that scrolls is scrolled 10 px above the keyboard as it opens, rising with the keyboard on iOS and at once under Reduce Motion; on a page with nothing to scroll, the browser's own reveal stays. When the keyboard closes, the page or scroll area goes back to where it was, sliding down with the keyboard on iOS, unless the person scrolled it meanwhile. In Firefox for Android on a slow device, Back can sometimes leave the page where the reveal scrolled it. A field in a scrolling area is scrolled 10 px above the keyboard when the area can bring it there; otherwise the page brings it into view. A field in a bar fixed at the bottom of the viewport rides up with the keyboard, the bar's bottom on the keyboard's top, and back down when it closes, even in a bar the app owns. A field inside a fully expanded Tall BottomSheet leaves that to the sheet. In a fixed container the app positions itself, such as a full-viewport dialog, a floating bar or a bar with its own
translate, a scroller around the field brings it above the keyboard when it can; otherwise the page brings it into view, or the browser's own reveal does. In Firefox for Android, where the page cannot scroll further, a field the page should bring into view can stay under the keyboard. Nothing changes under a mouse or a trackpad. - Under a finger, a full swipe on an
ItemorListItemswipe-action row works like a UIKit list row's, the same on every touch device. Past the open width the entries ride the row and the outermost action stretches out to the edge. Dragged on past the confirm point, judged on the finger as UIKit does, the row runs ahead and the outermost action covers its place. Letting go there fires it at any speed; backing out undoes that and closes the row. On a side with two or more actions, a full swipe confirms only from the open row. A disabled outermost action never confirms. - A trackpad's two-finger swipe moves an
ItemorListItemswipe-action row with the fingers from its first event past 8 px and, when they lift, settles it on the nearest stop at their speed, without stopping first. Within one swipe an open row only closes, and a long fast swipe fires the outermost action where a full swipe may. A mouse wheel's notches never swipe a row. - Under a finger, swipe actions on
ItemandListItemmove like a UIKit list row, the same on every touch device. The row stays under the finger, one for one, until the release, and settles on UIKit's own spring from where it is and as fast as it was moving, so a release no longer stops dead and restarts. The settle plays on the compositor, so a busy page cannot hold it back. A flick opens the row or closes it, by its direction. Under Reduce Motion nothing a release starts travels or springs: the row cross-fades to where it lands, asdesign:reduced-motionasks. A finger that lands on a moving row catches it instead of being ignored until the row stops. - Pagination: page links. Pass
getPageHrefand the page number, previous, next, first and last controls render as real links to each page's URL, so a page opens in a new tab, its address can be copied, and it works before scripts load.getPageHref(page, pageSize)returns the URL in the shape your app uses: a query parameter, a path segment, an offset or a cursor.assets the link component, as on Button, andLinkProviderapplies too.onChangestill runs when a link is activated: use it for state or analytics, and do not navigate in it, because the link navigates. The dots, the page box and the page-size selector are not links and work as before. A control that stops being a link while it holds focus, at the first or last page or while the pagination is disabled, keeps that focus. A Pagination withoutgetPageHrefis unchanged. - Pagination's first and last controls in the row reflect
data-first="first"anddata-last="last"on theirpagination-itemtarget, so a theme that joins the controls into one strip can round the outer corners on the end cells and leave out the separator after the last. The default look does not change. usePopovertakes ananchorRef: a ref to the element the popover sits on when it is not the control that opens it. Any element with a CSS box works (an HTML element such as a card or a table cell, or an<svg>element; a shape inside an<svg>warns in development). The trigger keeps its toggle and ARIA, and the anchor gets neither. The ref is read when the popover opens, on each render of your component, and on eachshow(), so a popover withhasLightDismiss: falsemoves between rows without closing when you setanchorRef.currentand callshow(). With light dismiss on, the press on the other row closes the popover first, andshow()opens it again on the new element. Ashow()before the ref holds an element waits, and opens when the ref is next read and holds one. A composition with an anchor and no trigger opens throughshow(). ThePopovercomponent and its ownanchorRefare unchanged.- Stepper: the current step's
step,step-indicatorandstep-labeltargets carry theselectedtheme state, the state tabs, side and top navigation and segmented controls use for their chosen item, so a theme can give the current step a selected look with aselectedrule on those targets. Screen readers still hear "current step". - Swipe actions on
ItemandListItemcome from one prop,swipe, whose valuecreateSwipemakes, from@astryxdesign/core/Swipeor the package root:swipe={createSwipe({leading, trailing, swipeBehavior})}. Each action has anid, and itsonActivatereceives{id, itemKey}: the action'sidand theListItem'sitemKey. So one definition at module scope serves every row; one whose handlers need component state goes inuseMemo. The swipe's type carries the ids, so an id it does not have fails to compile. A new value with the same ids keeps an open row open, and one with other ids closes it. The swipe's code comes withcreateSwipe, so a row givenswipeis swipeable at its first paint, and an app that never imports it ships none of it. TheswipeActionsandswipeBehaviorprops and theItemSwipeActionandItemSwipeActionstypes are deprecated (DEP-0017) and are removed in the next minor release.ItemSwipeActionVariantandItemSwipeBehaviorstay, and the new API uses them. Until then the deprecated ones keep working, with the swipe behavior this release gives every row, and whenswipeis set too,swipewins.astryx upgraderewrites static uses and gives each action anid. Before:tsx<ListItemlabel="Inbox"swipeActions={{trailing: [{label: 'Archive', onActivate: archive}]}}swipeBehavior="commit"/>After:tsximport {createSwipe} from '@astryxdesign/core/Swipe';const inboxSwipe = createSwipe({trailing: [{id: 'archive',label: 'Archive',onActivate: ({itemKey}) => archive(itemKey),},],swipeBehavior: 'commit',});<ListItem label="Inbox" itemKey={message.id} swipe={inboxSwipe} />; - A table header cell whose heading is cut short shows the full heading in a tooltip when keyboard focus reaches a sortable header's sort control; a mouse hover shows nothing, as before. Headings that fit show no tooltip, and screen readers hear the heading once.
- A data-driven Table's column headings now follow its
textOverflow, like the body cells. Under the defaultwrap, a heading longer than its column wraps onto more lines instead of ending in an ellipsis, so on a phone each column still says what it holds. Children-mode tables keep each heading on one line and grow its column to fit it, as before. UndertextOverflow="truncate", headings stay on one line and end in an ellipsis, as before. - A body row of a data-driven
Tablecarries thetable-rowtarget'sparity(data-parity="odd"for the first, third, … row;"even"for the others), and every row anisStripedtable may stripe (body and footer rows, not the header row) carries itsstripedstate, so a theme can style either stripe, for example odd-row striping only where the app stripes:components: {'table-row': {'parity:odd+striped': {backgroundColor: '#f9f9f9'}, 'parity:even+striped': {backgroundColor: 'transparent'}}}(the second rule clears Core's own even stripe; in ahasHovertable it also replaces Core's hover color on those rows, so give the stripe rules a:hoverof their own to keep one). Core's own stripe stays on even rows and the default look is unchanged. Rows a caller places in aTableBody(children mode) carrystripedbut noparity. A theme's background ontable-row(a stripe, or a hover) also reaches a pinned column (useTableStickyColumns), whose cells replay the row's fill; Core's theme build now lowers a component's pseudo-class blocks (:hover) like its resting rule: derived variables, container padding andreplaces; pseudo-element blocks stay as written. - A table row that
useTableSelectionselects carries thetable-rowtarget'sselectedtheme state, so a theme can style selected rows (components: {'table-row': {selected: {…}}}). The selection wash stays as it was; a theme recolors it by setting--color-accent-mutedin that state. - A theme's component overrides can hold
@lightand@darkblocks: properties, pseudo-class overrides and pseudo-elements that apply only where the element's color mode is that mode, asThemeresolves it from its ownmode, the system preference, or aMediaThemesurface. Inside media surfaces the nearest surface decides, for up to five surfaces of alternating modes nested one in another, so a lightMediaThemeinside a dark one (a toast over a dark surface) takes only the light block. Where no enclosing mode matches, the block writes nothing, so every other rule applies there as it would without it, and it can be any value, not only a color. Themes without these blocks compile to the same CSS. - TopNavMenu items and TopNavMegaMenuItem take
hasCloseOnSelect(default true), as DropdownMenuItem does: set it to false to keep the menu open after a pick, for an action that reports its result on the item.
Fixes
AppShell: on a phone, when the theme keeps the standard width points, a server-rendered page no longer shows the inline side navigation for a moment while its script loads. The menu toggle still arrives with the script.AvatarGroupOverflowtakes a caller'saria-labelas its name. Before, the translated "{count} more" always replaced it, so a builder could not give the indicator a fuller name such as "Show 5 more teammates". A calleraria-labelledbystill names it, and with neither the translated count does.Badgeis as wide as its label. A badge alone in aGridcell or aVStackno longer stretches into a bar across the cell or the stack; in a crowdedHStackit still shrinks and ends its label with an ellipsis.- A Breadcrumbs menu crumb's menu keeps its gap below the crumb and slides in from it again in published builds, and keeps the viewport gutter on its far edge.
- Calendar's weekday names no longer run into each other when a theme sets a larger text size or smaller element sizes. Each weekday column is at least as wide as its name. In a Calendar wider than its natural width, each weekday name now sits at the centre of its day column; at its natural width the Calendar looks the same.
- ChatComposer keeps its send action inside the composer on a narrow screen. When the footer actions are wider than the footer, they wrap onto more lines inside the composer instead of pushing the send button past its edge; an action too wide for a line of its own is shortened with an ellipsis. Wide composers look the same as before.
- In development,
ChatToolCalls,ChatDictationButtonthrow an error that names a missing required prop and shows the fix, instead of a TypeError from inside the component. Production output is unchanged. ChatToolCallsinside aChatMessagenow truncates a long target with an ellipsis on a narrow screen, instead of running past the message column.- The chat composer's @-mention and slash-command menu resolves its default "No results" message through the locale catalog, so a translation supplied to
InternationalizationProviderreplaces it. Before, it was a fixed English string. A trigger's ownemptySearchTextstill wins. - ChatComposerDrawer rounds its top corners and its tuck under the composer with the composer corner, so a theme that sets
chat-composerborderRadius moves the drawer with the composer. Outside a ChatComposer the drawer still uses--radius-chat. Shipped themes look the same. - A required
CheckboxInputis no longer announced as invalid before anyone touches it. Chromium reported an unchecked required checkbox as invalid from its first render, so a screen reader said "invalid" on every required checkbox of a fresh form. The invalid state now followsstatus, as onSwitch, and native validation still blocks a form submitted with the box unchecked. - A theme sets the room between a checkbox or a switch and its label with
gapon thecheckbox-inputorswitch-fieldtarget, for examplecomponents: {'checkbox-input': {base: {gap: '3px'}}}. Before, that gap sat on an inner row no target reaches, so the only way to change it was the--spacing-2token, which also changed the status message's padding. The default room stays 8px, and a hidden label still keeps no gap. - Citation: a label citation with a source icon no longer rides above the line inside a sentence; it now sits centred on the line, as a label without an icon already did. A paragraph that contains an icon citation can be 2 px taller. A number citation stays a superscript.
- In development,
Citationthrows an error that names thesourceprop and shows the fix, instead of a TypeError from inside the component. Production output is unchanged. CodeBlock's andTimestamp's copy buttons no longer update after they unmount: a clipboard write that finishes once the control is gone sets no state, starts no timer and announces nothing.- Copy works inside a frame that does not allow the async Clipboard API, such as a sandboxed artifact viewer or an embed. There
useClipboard, and so the copy buttons ofCodeBlock,Timestampand Markdown heading links, copy with the browser's copy command inside the reader's click or key press, also in an open modal dialog or a hover card, without moving focus. Before, those buttons copied nothing there (CodeBlockandTimestampshowed a failed copy), and the browser logged a permissions-policy violation for each press. Where the async Clipboard API is allowed, nothing changes. - CodeBlock's run-time highlight stylesheet now sits in the
astryx-basecascade layer, like the rest of Core's CSS. A theme's syntax colours and an app's own--color-syntax-*or::highlight()rules now win over CodeBlock's defaults in any load order, also for a CodeBlock in a portal under a root Theme. - In development,
CodeBlockthrows an error that names thecodeprop and shows the fix, instead of a TypeError from inside the component. Production output is unchanged. - On right-to-left pages, CodeBlock and Code keep code in its own direction: punctuation stays where it was written, a long left-to-right line starts at the visible edge and scrolls toward its end, and inline code inside right-to-left text reads in source order. Each code line takes its direction from its first letter, on any page, so a line that starts with an Arabic or Hebrew letter reads right to left from the line's end (when it is wider than an unwrapped block, its start sits at the far end of the scroll); other code looks the same on left-to-right pages. CodeBlock's line-number gutter, header and controls still follow the page.
CodeBlockscrolls a long line, or code pastmaxHeight, before script runs and in a page that runs none, such as a file made withastryx experimental render. Until now the code was cut off at the edge of the block until script measured it, and in a static page it stayed cut off. The code viewport still becomes a Tab stop only while its code overflows.- Core's compact StyleX media key matched at exactly the
mdwidth point (768px) and at exactly 500px tall, because StyleX rewrites(width < 768px)to a length the browser rounds up to 768px. The key now matches only below those edges, as the compact definition says, and Core spells every range-syntax width and height edge through one set of helpers. No component uses the key yet, so nothing changes on screen. - ContextMenu: in a bottom sheet, a data sub-menu whose label is not a plain string (for example emphasized text) now names the sheet after that label's text while its level shows, as DropdownMenu does. Back returns the root name.
- A CodeBlock title or language label too long for its header wraps before Copy and any caller controls, at a space or anywhere in a long file name, instead of running under them on a narrow block or with a wide code font.
defineThemenames a token map that holds itself ("tokens refers to itself: the value of self holds an object it sits in …") instead of recursing until the call stack overflows, when the theme extends one with adaptations. Themes whose tokens hold no such loop build as before.- A Dialog's and a Drawer's header row now contains its title, close button and end content. A theme that paints the header row (a title bar) no longer sees the title spill above and below it. Every slot stays where it was, so a theme that leaves the row unpainted draws the same pixels.
- Text that sets no color of its own (such as a selected nav row) in an open MobileNav, Dialog, Drawer or BottomSheet now draws in the theme's text color. Before, it took the browser's dialog default, which ignores the theme and drew black on dark panels. A Toast's text takes the side that reads best on its card, and the default top-layer viewport passes the page's text color down instead of the browser's. A dark-mode error toast now reaches 4.5:1. Before, it read about 4:1 in an in-place viewport.
defineTheme({extends})refuses a base written as a plain theme object (a name and tokens, not built bydefineTheme()) with the named "extendsmust be a theme from defineTheme()" error. Before, it merged the object's raw values, so a light/dark pair was written as#fff,[#000](https://github.com/meta/astryx/pull/000). A base fromdefineTheme()or a built theme module merges as before.- A toast shown from inside a
Themewith noLayerProviderdraws under that Theme and its mode, and follows it while the Theme is mounted, so its text reads even when the host page rewrites<html data-astryx-theme>(an artifact viewer that themes its own frame). A toast shown with no Theme around it still follows<html>. A toast that replaces another byuniqueID, one shown with a Theme and the other without, keeps drawing as the first one did, so the card stays in place. - Text inside a
Themethat sets no size of its own now uses the theme's body size, 14px by default instead of the browser's 16px. Plain text in a Card or Stack, a Blockquote's quote andText type="inherit"follow the theme's--text-body-size, as Core's own body text does, and move when a theme changes its text size. Text outside a Theme, and a host app's own styles, are unchanged:reset.csssets no font size. To keep 16px inside a Theme, set a font-size on your own container inside it, or set--text-body-sizein your theme (which also sizes Core's own body text). - defineTheme: a typography weight that reaches Core as a number (from a theme written in JavaScript or read from JSON, such as
heading: {weight: 700}) is written as its text (700) everywhere it is read. A theme that extends a base with adaptation rules now builds instead of failing with "adaptations.rules[0]… must resolve to a concrete CSS string". TheFontWeighttype does not change. - The active option of a select, multi-select and typeahead list (the one the keyboard or pointer is on, named by
aria-activedescendant) carries ahighlightedtheme state on its row target, as Item and CommandPaletteItem rows do:selector-option-row,multi-selector-option, and the typeahead's option row, which gets its own target,typeahead-option(withsizeandselected). A theme can style the highlighted option without a structural selector. - The radio's circle (RadioList, the menu radio, and every host of the shared radio indicator), its dot and its pressed layer are drawn at a 50% radius instead of the
--radius-fullpill token, so a theme that squares its pills keeps round radios. A theme that wants square radios overrides the radio component. Theme's runtime style injection hint no longer names a package or an import made up from the theme's name (@astryxdesign/theme-canvas-editor/built,canvas-editorTheme). It gives the build step,astryx theme buildon the file that defines the theme with--detail full, whose printed import lines bring in the built .js and .css; a theme from an Astryx theme package ships both built.- Core's install note no longer tells a project that keeps its Astryx guidance as a project skill (
astryx init --to skills, or a folder in the project) to runinit: the setup check also counts the Astryx project skill in.agents/skills,.claude/skills, or a project folder astryx.config saves (astryx init --to ./<folder>), read from the config's text without running it. - The switch thumb is drawn at a 50% radius instead of the
--radius-fullpill token, so a theme that squares its pills squares the switch track and keeps a round thumb. A theme that wants a square thumb sets the radius onswitch-thumb. - A theme value left
undefinedin a part's style block, a color-mode block (@light,@dark), a pseudo-class block, anonDark/onLightsurface or an adaptation rule's parts is now not set, and so is a component, style key or color-mode block leftundefined, or one whose every value is, as a page token leftundefinedalready was: the stylesheet writes nothing for it. In a style key or a color-mode block, the value the theme inherits for that property stays. A restated pseudo-class block still replaces the inherited one whole, even when every value in it isundefined: it stays, empty, and its component counts as themed. Before, the stylesheet held the textundefined(padding: undefined;), which the browser drops, and the inherited value was lost too; in an adaptation rule,defineThemerefused the theme. Anullvalue keeps its meaning: it replaces an inherited value and is written as it is, and an adaptation rule still refuses it. defineThemetreats a local token leftundefined(in the theme or in an adaptation rule'slocalTokens) as not set, as a token, or a value in a part, surface or adaptation rule, leftundefinedalready is: the theme builds and the stylesheet writes nothing for it. Before, it was refused as no CSS string, so a conditional spread or an unset environment value failed the theme. An adaptation rule that writes a local token name no theme in the lineage declares still fails with its name.localTokens: undefinedat the root is refused by name ("localTokens is undefined: omit the field or pass an object"), asextends: undefinedis: a rootlocalTokensorextendsleft undefined is almost always a failed import.- defineTheme: a theme's own token map that holds itself is named as the theme's
tokens, not as one of the adaptation rules of the theme it extends; and an adaptation rule's value or condition that holds itself is refused by its path (adaptations.rules[0].value.tokens.self …) instead of overflowing the stack. - A toast's card draws on the right side from the first paint on a system-mode page. Before a script ran, a reader in dark mode saw the info toast with light text on its light card (about 1.1:1). The toast now renders its light-page side and names its dark-page side beside it, and the theme draws that side on a dark page. Themes whose toast surfaces keep one side in both modes write no extra CSS.
- Toast: before the surface is measured (a server render, a static page), the Toast's text side comes from the theme's own resolved inverted surface color, by the same rule the measurement uses, instead of assuming the surface is dark in light mode. This applies when the inverted surface is an opaque hex,
rgb()/rgba(),blackorwhitevalue and the on-dark and on-light colors are hex,rgb()/rgba(),blackorwhitevalues; any other value (such as a translucent surface,oklch(),hsl()or another named color) still starts from the color mode until the measurement runs. A theme whose inverted surface is a light hex orrgb()color in light mode no longer renders a Toast with white text on a white bar until the page runs its script. - In dark mode, secondary text on a neutral fill (an unselected SegmentedControl label, AvatarGroup's "+N" count) now meets 4.5:1 contrast on the default surface and on a Card. The default dark
--color-text-secondaryis a little lighter:#B0B5BB, was#AAAFB5. - Under Reduced Motion, releasing a mouse drag on a date or time wheel lands on the nearest row at once instead of gliding to it.
- In development,
DateRangeInputthrows an error that names thevalueprop and shows the fix, instead of a TypeError from inside the component. Production output is unchanged. - Dialog: opening a dialog no longer moves focus to a
data-autofocusfield (such as aTextInputwithhasAutoFocus) inside a closed dialog nested in it. A nested dialog's focus request belongs to that dialog alone. Before, a closed nested dialog whose box was still laid out (for example through a display utility class) could take the caret into a field nobody could see. - Dialog: a DialogHeader that mounts after the dialog opens now names the dialog, and the name goes away when the header unmounts. A dialog's own
aria-labeloraria-labelledbywins, and anaria-labelthat arrives while the header is mounted now names the dialog instead of losing to the header title. useSpeechRecognitionandChatDictationButton: a page rendered on the server no longer has a hydration mismatch. The server and the render that hydrates its markup both reportisSupported: false, so they draw the same tree; the dictation button appears in the next render when the browser supports speech recognition.- A
DropdownMenuwhose layer opens after its trigger becomes a valid anchor now takes focus as it opens, and firesonClickonce. A menu in a native<dialog>that the page displays closed opens one commit after the press. The menu read that open as refused, so focus stayed on the trigger andonClicknever fired. - DropdownMenu: a mouse press opens a menu whose trigger sits in a same-origin iframe or another window, and the menu stays open through that press's release
- DropdownMenu: in a bottom sheet opened from the keyboard, focus stays on the row a person moved to when the menu re-renders with a new
itemsarray, such as after a choice that updates the app's state. It moved back to the first row before. The sheet still focuses its first row when it opens, and its heading when a sub-menu is entered or left. Reported by duytbp. - A DropdownMenu sub-menu whose
labelis not a string, such as emphasized text or a translated message component, is now named correctly: a drilled-in view is named by the label alone, not by the whole row with its description; a view nested in it names its Back row "Back to" that label; and in a bottom-sheet data menu the sheet takes that label's text as its name while its level shows. Sub-menus with string labels do not change. - A layer's exit copy, which a touch close plays on, keeps the padding, border and colors of the element it copies. Before, the browser's popover style padded, bordered and painted it, so a surface with no padding of its own drew its content inset during the close.
- Field labels use the primary text colour. A label names its control, so it now reads at full strength, while its description and the Optional or Required marker stay in the secondary colour. Before, the label and its description shared one colour.
- Field labels use the semibold weight. Arial, Helvetica, Liberation Sans, and Segoe UI have no medium face, so a medium label drew in their regular face, at the same weight as its description. The label now draws in the next heavier face: semibold in Segoe UI, bold in Arial, Helvetica, and Liberation Sans. With fonts that have a medium face, such as the Apple and Android system fonts and the first-party theme fonts, labels become one step heavier. CheckboxInput and Switch labels use the same label style and change too.
- Malformed component icon slot values no longer throw while formatting diagnostics. Invalid fields keep the component fallback without dropping valid sibling fields, and production skips diagnostic formatting.
- MultiSelector's caller-rendered trigger exposes its disabled state and blocks caller activation handlers, including when read-only or disabled by InputGroup, while remaining focusable.
- An
Itemwith its ownonClickorhrefno longer rings the whole row when a control in itsstartContentorendContenttakes focus, and aToken's remove button no longer rings the whole token: each of those tab stops shows one focus ring. Rows that delegate to a nested control, and reorderable rows with a handle, keep their ring as before. - Tab moves through a
Popoveror aDropdownMenuthat opens inside a native<dialog>that the page displays closed. Tab and Shift+Tab wrap at the layer's edges, and aDropdownMenu's header and footer are Tab stops again. The focus trap counted every control in a closed dialog as hidden, so it found no Tab stops and held focus in place. A closed dialog that the page displays has a box, so its controls are Tab stops. A closed dialog withdisplay: nonehas no box, and its controls stay out of the Tab cycle. - A mouse drag in a page shown in a sandboxed frame (such as an embed or a viewer) that is released outside the browser window now ends when the pointer comes back over the frame or presses again. Before, a Slider thumb or a pan stayed held and followed the pointer with no button down.
- Grid:
columns={{minWidth}}withoutmaxno longer overflows a container narrower thanminWidth. A lone column now shrinks to the container width, as it already did withmax, so a phone no longer scrolls sideways. In a container that takes its width from its content (an inline-block, or a flex item with no width), an uncapped Grid is now as wide as its content instead ofminWidth, as a capped Grid already was. Headingwithout alevelfrom 1 to 6 renders as anh2and warns in development, instead of failing with "Element type is invalid". A numeric string such aslevel="3"keeps rendering its level, and now warns in development.- Built-in text in six components that was fixed English now follows the locale. Through the catalog, so a provider's translation or override replaces it: Tokenizer's
+N moreoverflow count, Slider's screen-reader "Required", CodeBlock's<language> diffheader label, the default label of a token made byuseChatPasteAsToken(the same message the pasted-text chip uses), and the relative-date choices in PowerSearch's popover editor (the touch sheet already translated them). Through the locale's own unit formatting: Timer's elapsed durations, which read34s,2m 08sand1h 05min English as before and use the locale's unit names elsewhere (German2 Min., 08 Sek.). Other English output is unchanged, except that Tokenizer groups the digits of a count of 1,000 or more; Timer's units are never grouped (1000h 05m, as before). Shipped locales show English for the new catalog keys until translators add them. Icongiven its glyph asname(as other icon libraries call it) renders that glyph and warns in development to useicon, instead of failing with "Element type is invalid".namedoes not reach the DOM.- The checkbox check and dash and the radio dot are sized as a share of their box, so a theme that sizes the box through the
checkbox-indicatororradio-indicatortarget'swidthandheightgets marks in proportion to it: a 13px box draws a 7.6px check and a 5px round dot, where before the 14px check was squeezed into the box's 11px inside, filling it edge to edge, and the 10px dot nearly filled the circle. The dot is rounded to whole pixels so it stays a circle. The shipped 20px and 24px boxes draw the same pixels as before in every official theme. A theme that sets the box'sborderWidthdirectly, rather than through--border-width, gets marks slightly smaller or larger by that difference. - The slot that holds a checkbox's box or a radio's circle in CheckboxInput and RadioList is as big as the mark itself, instead of a fixed 20 or 24px. A theme that sizes the box (for example 13px) now gets the label right beside it and a pressed layer that fits it, where before the box floated in an empty 24px slot. The hidden input keeps its 20 or 24px hit area (at least 24px on touch screens), centered on the mark, and the focus ring stays on the mark. The shipped look is unchanged. A row is as tall as its mark or its label, whichever is taller: with a 13px box a default-size row goes from 24px to about 20px. A theme with a replacement indicator (
defineTheme({indicators})) of another size sees its rows tighten: the label moves closer by (24 − size) / 2 px at the default size, the row is as tall as the mark or the label (the probe theme's 16px marks: 24px to about 22px), and the pressed layer matches the mark. A Markdown task item drawn in its list's marker column keeps its checkbox centered on the item's first line at any box size. - On an interactive Item or ListItem row (with onClick, href or a delegated control), the current marker (
aria-current) is now on the element that takes focus, so a screen reader announces "current" when the row's button or link is focused. Before, it sat on the row's root, so a screen reader did not announce it on the focused button or link (WCAG 2.2 SC 4.1.2, Name, Role, Value). Rows whose root takes focus, and rows that are not interactive, keep it on the root. A selected row still carriesdata-selectedon its root and looks the same at rest; while it slides past other rows, a selected row now keeps its fill whatever itsaria-currentvalue. - An open swipe-action row on
ItemandListItemcloses on a touch tap on its own content, as a UIKit list row does, and that tap no longer activates the row or paints its press. It also closes when the list or the page scrolls, including a scroll that starts on the row itself, unless focus is inside its open panel (the browser may be scrolling a focused entry into view), and it counts as open from the release that opens it, before its spring comes to rest. - Swipe actions on
ItemandListItemrun on the gesture system. A row claims a sideways touch at 8 px, before a browser commits to scrolling it. From the claim the row follows the finger one for one, so the part under the finger stays under it. A pen now swipes the row as a finger does. A second finger that lands before the claim leaves the touch to the browser's pinch; once the row has claimed its finger, a second finger no longer cancels the swipe. The click a browser synthesizes after a swipe is cancelled at its source instead of being swallowed by a 400 ms timer. - In development,
Kbdwithout akeysstring (for example with children, or an array) throws an error that names the prop and shows the fix, instead of a TypeError from inside Kbd, such as "Cannot read properties of undefined (reading 'split')" or "keys.split is not a function". Production output is unchanged. - A released input hold no longer changes its layer. A closing BottomSheet's hold reads focus a moment after focus leaves the sheet; if the hold was released in between, that late read could leave the sheet inert and hidden from assistive technology. No browser flow is known to hit this today.
- Every anchor-positioned layer (Popover, DropdownMenu, Selector, Tooltip, and other
useLayersurfaces in anchor mode) stays on screen when its trigger runs partly past the viewport edge, such as a control in a panel that scrolls sideways, as long as the layer fits between the viewport gutters. Layers now place themselves withanchor()insets against the viewport instead of a position area that grows to include the trigger. Popover,Tooltip,HoverCardand the other anchored layers open again when their trigger sits in a native<dialog>that the page displays closed. Such a dialog never enters the top layer, so its trigger is a valid anchor. The layer waited for the dialog to open, and it never opened. A layer still waits for aDialogthat displays its element before it callsshowModal().Dialog,Drawer,LightboxandMobileNavopen their dialog in the Effects of the commit that displays it. A trigger with a box in a closed dialog now waits for one more commit. React runs those Effects before it renders that commit, so a dialog that is still closed then stays closed, and the layer opens at once. For a press, that commit runs before the press's task ends, so the layer and its initial focus land within the press. A closed dialog withdisplay: nonegives its trigger no box, and the layer still waits for it with no time limit.A secondshow()while a layer waits for the same trigger keeps that wait. It no longer restarts it.- Popover and DropdownMenu, in their popover presentation, and Dialog move focus as they close only when the close would strand it (WCAG 2.2 SC 2.4.3, Focus Order). Focus that used to fall to the page body when the opener was gone now goes, in order, to the element focused when the layer opened, its trigger, the control that names the layer in
aria-controls, the component's own stand-in (a typeahead's input), the anchor or the first control inside it, the opener's former place in its group, the nearest surviving ancestor, the layer that opened this one, then the page'smainregion. A released behavior also changes: a DropdownMenu no longer focuses its trigger at close when focus never entered the menu. TheuseFocusTraphook shares the trap that Popover uses, so it returns focus the same way. A Drawer keeps its own return at close and gets the shared one only when it is removed while open. There is no option to turn focus return off. To send focus somewhere specific, focus it inonOpenChange(Popover, DropdownMenu) or inusePopover'sonHide; for a Dialog, focus it after the dialog has closed, since the page outside an open dialog is inert. A Popover or DropdownMenu returns focus before the browser's own restore, so its trigger gets a focus ring only after keyboard input. - Lightbox: an open caption that ends in a block image wider than the room beside "less" keeps its text lines when the window widens, instead of growing by a line every frame. "less" takes the line below the image. (#11740)
- An open Lightbox caption that widens to fewer lines no longer forces a layout in the frame that shrinks it. That holds for a caption of text, inline elements, inline-blocks, images, and paragraphs or other plain blocks with no room under its last line. Anything else takes the exact read, as before: one forced layout. That includes floats, drop caps, flex, grid and clipped blocks, and empty inline-blocks. It includes room under the last line of text, such as bottom padding or a trailing line break. It also includes list markers, text indents, justified last lines, and
::beforeor::aftercontent outside an inline element's boxes. - In block and inline layout, a Link whose label has no break opportunity, such as a bare URL from
useLinkify, now wraps inside its line instead of running past it and making the page scroll sideways. The Link stops at its container and its label may shrink, so its text wraps. In a flex row, a Link whose label is wider than the row is now capped at the row's width and wraps. A Link in a line wide enough for its label looks the same. A content-sized grid or table column still grows to the label's longest word. - In development,
TreeList,Outline,TopNavMenuthrow an error that names a missing required prop and shows the fix, instead of a TypeError from inside the component. Production output is unchanged. - Markdown bulleted and numbered lists stay inside their column: a list no longer reaches 8px past both edges, so Markdown that fills a phone screen no longer makes the page scroll sideways. Markers and text keep their positions.
- Markdown task lists stay inside their column: a list of checkbox items no longer reaches 8px past both edges, so it no longer makes a phone-width page scroll sideways. Checkboxes and text keep their positions.
- A bottom-sheet DropdownMenu, MoreMenu or ContextMenu opened before its sheet code has loaded (a press right after the page loads) now shows the sheet together with its actions, instead of an empty sheet for a moment first.
MetadataListItem: a value no longer breaks an ordinary word or number mid-way when its row is tight, such as an amount beside its description on a phone with a wider font. A word longer than the whole line still wraps.- MobileNav keeps its link to MobileNavToggle when a caller passes
id={undefined}: the dialog keeps AppShell's drawer id, so the toggle'saria-controlsstill names the drawer. A definedidstill replaces it. - MobileNav with
side="auto"opens from the opener's inline edge in right-to-left layouts. When the opener holds focus, that is used. When nothing is focused (such as the first open after a page load), the opener is found through itsaria-controls, which AppShell'sMobileNavTogglesets. A custom opener withoutaria-controlsthat never takes focus still opens fromend. MultiSelectorwithhasSearch: the trigger button no longer carriesaria-required, which ARIA does not allow on a button (WCAG 2.2 SC 4.1.2, Name, Role, Value). Before, the button carried it, an attribute a button may not have. A required field still says so: the field label's visible marker is part of the trigger's name, or a hidden "Required" description is added when the marker is not shown, and the search box carriesaria-requiredwhile the list is open. This matchesSelector.- A
NavHeadingMenupassed as themenuof aSideNavHeadingorTopNavHeadingno longer adds a second, unnamed menu inside the heading's menu. Screen readers now meet one menu, named after the heading, that holds the items. ANavHeadingMenuused on its own is still a menu, named by thearia-labelyou pass. - Icons,
useIcon, and component icon slots use the nearest Theme's object, so registering or nesting another theme with the same name does not replace their artwork. Icons outside a provider keep the registered root-theme fallback. - A neutral Badge in a primary or destructive Button now meets 4.5:1 contrast in light and dark mode. It paints the Button's own colour pair inverted: the Button's content colour as the badge fill and its fill colour as the badge text.
- Outline: under reduced motion, following a link lands on the heading at once instead of scrolling there, the active indicator moves at once instead of sliding, and a link's hover and current colors change at once. A caller's
aria-labelnow names the navigation, in place oflabeland the default name. - OverflowList: in a theme whose spacing scale differs from the default, or when the root font size changes, the list now fits items with the gap it actually renders, so the last visible item and the overflow indicator are no longer cut off at the list's edge.
- Popover: a closed popover's trigger no longer points at the popup with
aria-controls, so it no longer references a popup that is not shown. The trigger names the popup only while it is open;aria-expandedandaria-haspopupare unchanged. A render-function trigger still receivesaria-controlsin its props. usePopoverkeeps its focus-return target whenshow()runs again after initial focus has moved inside the popover, so a close returns focus to the element that opened it instead of losing it.- A press no longer scales a trigger whose own layer is open: a Button that opens a menu or a Popover, and a ghost or secondary Selector, MultiSelector or ComplexSelector. Under a mouse or a finger, the open layer stays where an unpressed open puts it. A disclosure button without a popup keeps its press.
- ProgressBar and CircularProgress fills reach 3:1 against their track (WCAG 2.2 SC 1.4.11, non-text contrast). ProgressBar's status fills take the status text colors, and its neutral fill, like CircularProgress's, takes the secondary text color instead of the disabled one, which is the bar's track color in dark mode in Theme Neutral and Theme Stone and under 3:1 on the bar's track in every bundled theme in light mode. A disabled bar takes the same fill and dims its track and fill to half opacity, as a disabled Slider or Switch track does, and a disabled ring dims as a whole, center content included, so each reads quieter than a neutral one. A mark on any fill but accent takes the surface color; in Theme Butter and Theme Stone, a mark on a status fill takes that status's on-color. CircularProgress draws every variant on the muted background track, ProgressBar's base track, because some themes' status muted colors are the status color itself. In Theme Neutral, Theme Butter and Theme Stone a dark neutral or disabled fill takes a lighter neutral stop, Butter's and Stone's status fills take the theme's status colors, Stone's accent fill takes a blue stop that reaches 3:1, and the CLI's bundled theme templates match.
- In development,
Markdown,SyntaxTheme,InternationalizationProviderthrow an error that names a missing required prop and shows the fix, instead of a TypeError from inside the component. Production output is unchanged. - Selector and MultiSelector keep their selection surfaces closed when mounted disabled with
isDefaultOpen, including when read-only or disabled by an InputGroup. - Tab from any radio in a
RadioListnow leaves the group, also from a radio that the app focused by script. Before, Chromium sent Tab from that radio to the group's checked radio when it came next, so the group took two Tab stops, and in a modalDialogthe result depended on where the group sat. - reset.css gives the page the
--font-family-bodyfont, so text in the page body outside the Theme wrapper, such as a tooltip or a hidden span a chart uses to measure labels, no longer falls back to the browser's serif font. A page where no stylesheet defines the token keeps its current font. - A focused
ResizeHandleacts only on its own keys: plain arrows, Shift with an arrow, Home, End and Enter. Any other combination, such as Alt, Control or Command with an arrow, Home, End or Enter, or Shift with Home, End or Enter, now passes through to the page, so the browser's own shortcuts on those keys (history navigation, scrolling to the top or bottom) and the app's own shortcuts run. - RichText text reads the way it is written, in either document, and the shared first-strong classifier reads three Arabic marks, the Rumi numerals, and the digits of Devanagari, Bengali, Tamil, Thai and other scripts by their bidi class, which changes
Markdownoutput too: a line opening०१ שלוםnow reads left-to-right where it read right-to-left before.Badge,TokenandInputGroupTextread the same strong set to decide whether their own text holds any right-to-left character, so the three Arabic marks — the semicolon, the question mark and tatweel — now count there too, wherever they sit in the label. A paragraph, heading, quote or list item takes the direction of its own text at any depth, so a Hebrew paragraph in an English document flushes right with its caret following the arrow keys instead of walking backwards, and an English paragraph, list item or table cell in a Hebrew document does the mirror. Each line of a fenced code block reads its own way too, so a Hebrew comment reads right-to-left whileconst x = 1;keeps its semicolon at the end. Top-level lists, tables and code blocks keep ordering their contents in the document's direction; a nested list follows the item that holds it. The stored value now drops adirthat arrives on them with pasted HTML or an older document. - On phones and tablets, a Table or CodeBlock that scrolls sideways now fades each edge that hides content. Those browsers show the scrollbar only while scrolling, so the fade shows there is more to see. With a mouse or a trackpad nothing changes. A viewport that fits does not change.
- In development, these components throw an error that names the missing prop and shows the fix, instead of a TypeError from inside the component:
Tokenizerwithoutvalue,PowerSearchwithoutconfigorfilters,PowerSearchFilterEditorandPowerSearchTokenwithoutconfig,TypeaheadItemwithoutitem, andComplexSelectorwithout achildrenfunction. Production output is unchanged. - Secondary text now reads on every palette tint. The default light
--color-text-secondaryis[#445564](https://github.com/meta/astryx/pull/445564)(was[#4](https://github.com/meta/astryx/pull/4)E606F), so secondary text on a gray Card or any other--color-background-<hue>tint meets 4.5:1 over the surface and the page body. The dark value is unchanged. To keep the previous light colour, a theme can set--color-text-secondarytolight-dark([#4](https://github.com/meta/astryx/pull/4)E606F, #B0B5BB). - SegmentedControl: when a page's own style wraps the segments onto two rows, a tap selects the segment it lands on, not the segment above or below it in the other row.
- Selector, MultiSelector, and ComplexSelector: the option list's trigger-width minimum is now clamped by the layer's viewport cap, so a trigger wider than that cap no longer makes the list wider than the cap.
- In development,
SelectorandMultiSelectorwithout anoptionsarray (for example with<option>children) throw an error that names the prop and shows the fix, instead of "options is not iterable". Production output is unchanged. - When an option grows while a
Selector's list is open, and the list is shorter than its height cap, the selected row stays on the trigger. The selected-item overlay measured its place only when the list opened, so a row that grew above the selection left it off the trigger, and a list near the viewport's end grew past it. The overlay now measures again when the open list resizes, before that frame paints. No API changes. - Selector, MultiSelector: focus returns to the trigger again after a mouse pick in a Selector and when a MultiSelector closes after a pick. It also returns after a press on a container around the list that is no Tab stop, such as one with
tabIndex={-1}. Before, inside such a container, as a dialog's content box can be, focus stayed on the container, so keyboard and screen-reader users lost their place. A press elsewhere still leaves focus where it lands, such as on another field or an unselected tab. So does a press on a container that is a Tab stop, such as a card withtabIndex={0}. - Selector and MultiSelector inside an open shadow root: after a press on a container around the list that is no Tab stop, such as one with
tabIndex={-1}, closing the list returns focus to the trigger, as it does outside a shadow root. Focus stayed on the container, because the close read the shadow root's host as the focused element. A closed shadow root hides its focus from the page, so there focus still stays on the container. - The setup reminder now says why to run
initnow: "Astryx is not set up in this project yet. Next step: runnpx astryx initnow, before you write Astryx code. It asks no questions, prints the getting-started steps, and saves the Astryx guide to AGENTS.md." Before, it saidinitwould "install the Astryx agent prompt", which agents read as a file change the user did not ask for, so they kept working without it. The command it names is unchanged, and so are the places it prints. - Three styles that set a shorthand after another style on the same element set one of its longhands now set the longhands instead: an ordered List with dividers (its row gap), a flexible vertical on-track Stepper connector, and the PowerSearch sheet trigger with tokens. StyleX resolves that order differently in Storybook and in the published CSS, so each state had two computed values. It now has one. Nothing changes on screen in either build. A new lint rule,
@astryx/no-shorthand-longhand-merge, flags the pattern. - A horizontal
Sliderwith labelledmarksnow keeps room for the labels: before, the labels hung below the slider's box and the content after it overlapped them; now that content starts below the labels. The labels take the supporting text's line height, so the room no longer depends on the surrounding text. Sliders without mark labels, and vertical sliders, keep their size. - useTableSortableState no longer throws when a sorted column holds an Invalid Date. The default comparator now treats an Invalid Date like null, undefined and NaN: it sorts last in ascending order and first in descending order.
- A field with an error, warning or success status shows keyboard focus again. The status style replaced the whole field shadow, so the focus ring disappeared and a focused field with a status looked the same as an unfocused one. It now keeps the focus ring in TextInput, TextArea, NumberInput, Selector, MultiSelector, the date and time fields, Typeahead, Tokenizer and PowerSearch.
- In a Stepper's compact horizontal layout, a disabled Step now tells screen-reader users it is unavailable, with a hidden word after its label, as the expanded layout's disabled button already does. The new translated string is
@astryx.step.status.unavailable; locales without it fall back to English. - A vertical
Stepperstep with separated indicators (the default) keeps its content within the step. Before, a wide field in an expanded step, such as aSelector, pushed the step's body past the step, so on a phone the page scrolled sideways, text was cut at the right edge, and a dropdown opened off-screen. Now the body shrinks to the step's width and the content wraps inside it. - The switch thumb rests as far from the track's end as from its top and bottom, at both ends, with a mouse and under a finger, read from the track's and the thumb's own sizes. A theme that sizes the track (
widthandheightonswitch) or the thumb (onswitch-thumb) now keeps the thumb at the ends, where before it stopped short or ran past the end, and under a finger jumped at release. The control's box now follows the track too: before, it stayed 32 by 20 or 40 by 24 and squeezed a wider track back to that width. To follow that one rule, the small switch's off thumb with a mouse sits 3px from the start (as under a finger), not 2px; and in forced colors (high contrast) every thumb moves up to 1px so it sits as far from its end as from the top: the on thumb with a mouse moves 1px in from the end, so it no longer touches the track's border, and the medium off thumb with a mouse and every thumb under a finger move 1px toward their end. Everything else draws the same pixels in every official theme. - BottomSheetSwitcher: a flow without its scrim (
hasScrim={false}) that closes with focus inside it now returns focus to the element that opened it, as a standalone sheet without its scrim does, instead of leaving focus on the page body. A switcher with its scrim that is removed while a sheet is open now returns focus to the flow's opener, when the removal lost focus, instead of leaving it on the page body. - Tab: a label that wraps, through
xstyle, stays centered in its tab, selected or not. An unselected label could take one line fewer than its selected (semibold) width, and it sat at the top of the tab, so selecting the tab moved it down half a line. A label on one line in a button tab looks the same as before. The one visible change for one-line labels: a link tab's one-line label sits centred in its reserved width, as button tabs already do. It moves sideways, toward the tab's center, by half the extra width its semibold weight takes: 1 to 3 px for a short label, depending on the label and the font. - A Table inside a Stack or another wrapper no longer reaches past its container's top or bottom padding. Before, a Table that was the last item of a Stack inside a Section, Card or Dialog pulled that Stack short, and the content after it overlapped the table's last row. Now a Table reaches a container's top or bottom edge only when it is that container's direct first or last child, the same rule its rounded corners follow. A Table that is a direct child looks the same as before, except when another Table or a bleeding List sits deeper in the same container: then the direct-child Table also keeps the container's padding at that edge, as its rounded corners already did. A Table nested in a Stack keeps the container's padding above and below it. Its sides still reach the container's edges as before.
- A Table column without
renderCell, the tree column of a tree table included, no longer throws or prints engine text when a cell holds an Invalid Date. The default cell renderer now shows an Invalid Date as an empty cell, as it does for null and undefined. Sorting already treats it as a missing value. - A Table in children mode whose cells wrap (the default) now scrolls inside its own box when it does not fit, as a data-driven Table does, instead of shrinking every column until words break letter by letter and headings are cut. Its columns now follow their content instead of sharing the width equally. A children-mode Table with
textOverflow="truncate"keeps its columns within its box and lays out as before. - With
useTableColumnsVirtualization, a horizontal scroll that changes which columns are mounted now renders only the cells of the columns that enter. Before, every mounted cell of every mounted row ran its plugin transforms and rendered again. Each body cell is now its own memoized element, so cells whose inputs stay the same skip both.useTableStickyColumnsnow returns a new plugin object when its pinned keys change, so changingstartKeysorendKeysat runtime pins and unpins body cells together with their header; before, body rows kept their old pinning until they rendered for another reason. - Table: with column windowing, a horizontal scroll that keeps the same columns mounted renders the table once instead of twice.
- A Table stays the one scroll region when a page host gives every table's parent
overflow-x: auto. Before, the box inside the Table scrolled instead, so the Table lost its keyboard stop and focus ring. - Table: in a narrow column, a header's label truncates before its sort indicator and filter button, so those controls stay inside the header cell and can be reached.
- In a Table with sortable and resizable columns, a sortable column's resize line now sits on the column divider, like every other column's, in left-to-right and right-to-left layouts. Before, it sat one cell padding inside the column. A sortable header's right-click menu still opens at the pointer.
- Table tree rows follow the disclosure pattern. Body rows no longer carry
aria-level, which ARIA allows only in a treegrid; Table has no grid keyboard model, so it keeps table semantics. Each parent row's expand/collapse button keepsaria-expandedand its "Expand/Collapse <row>" name, and while expanded it names its child rows witharia-controls. Indentation stays visual. No visual change. - In development,
TableSelectionToolbarwithoutselectionthrows an error that names the prop and shows the fix, instead of a TypeError from inside the component. Production output is unchanged. - TextInput (outside an InputGroup) and TextArea: an error status without a message now gives screen readers text: the field is described by a hidden, translated "Invalid value", so assistive technology hears that the value has an error. In development the field also warns that the error has no message. Nothing changes on screen; give
status.messageto show the error in text. - TextInput: a standalone field grows to hold its text line when text is enlarged, instead of the line running across its borders. At the default text size each size keeps its height (28, 32 and 36 px).
- A theme that gives a Card, a Dialog or a menu corners of different radii (
borderRadius: '12px 12px 0 0'or a corner longhand such asborderStartStartRadius) now reaches what those components hand each corner to: a full-bleed Table or a bleeding List in a Card or a Dialog takes each corner as the container draws it, focus ring and row fills included, and the rows of a pointer menu (DropdownMenu's popover and sub-menu flyouts, and ContextMenu), sub-menu rows included, take the menu's shape less its padding; the touch sheet's list rows, and a drilled-in sub-menu view with its own header or footer, keep their own corners. An elliptical corner (8px / 4px) reaches a full-bleed Table; a List and menu rows subtract the padding from it, so they keep square corners there. A default Card, Dialog or menu inside a themed one keeps its own corners. Before, these children kept square corners, or took the first corner's radius at every corner when the CLI theme editor wrote the radius. The theme pipeline writes each corner to its own private variable for components whose derivedborderRadiusentry sets the newcornersflag. A radius of one value draws as before. - A theme that styles
linkkeeps Core's hover tint on a link's color: the rules that hold each linkcolorprop's color now hold, on hover, Core's tint of that color, so a link setting of any kind (a color for one mode, or any theme link color) no longer removes the hover tint in that mode. A theme's own hover color for a link color key still wins over the tint. - A theme's
@darkand@lightcomponent styles under asystemThemethat no Theme around it forces to light or dark now follow the scheme the page root draws in: the root'scolor-scheme, else its<meta name="color-scheme">(acolor-schemeonbodyor a container does not count). On a page that draws in one scheme, such as a page that names no scheme (noreset.css, nocolor-schemeon the page root and no<meta name="color-scheme">), which draws light, the styles of that scheme apply whatever the reader's device is set to: a reader whose device is set to dark no longer gets the theme's dark component styles on the light page, and gets its light ones. On a page that follows the reader, the styles follow the reader's setting as before. At the first paint of a server-rendered page, before the rootThememounts, they follow the reader's setting. Themeno longer stops the page whenthemegets a value that is not a defined theme, such as the mode string"light", a plain object orundefined. That Theme applies no theme of its own: its subtree keeps the theme around it, or Core's default tokens at the root, and still takes itsmode. The server and the browser render the same markup. In development a warning names the value, and for a mode string it points to themodeprop.- A
Themeinsystemmode now takes the light or dark scheme of the page around it. A host that draws the page dark, such as an artifact viewer in its dark theme, now gets the dark theme inside theThemetoo; before, everything inside it followed the device's setting, so a reader on a light device saw dark text on the host's dark page.useTheme()anduseSyntaxTheme()report the same mode, so charts and canvas match: asystemTheme resolves to the scheme the page root names (light when it names none), else the device's setting, and under aThemethat forces light or dark it follows the device. If your app sets the page root'scolor-schemetolightordarkitself, that setting now decides what asystemTheme shows.useSyntaxTheme()also follows aThemethat forces light or dark, as code blocks do.reset.cssmakes the page root follow the device's light or dark setting. Core's stylesheet, prebuilt or from a source build, sets no scheme on the page root. An app that does not loadreset.cssand names no scheme (nocolor-schemeon the page root and no<meta name="color-scheme">) stays light, and so do Astryx's tokens anduseTheme()there; a theme's own@darkcomponent styles still follow the device on such a page. To follow the device everywhere, import@astryxdesign/core/reset.css, or setcolor-scheme: light darkonhtml.useTheme()also reads the page's<meta name="color-scheme">, as the browser does. - A page that renders a Button or an Icon but no
Themeno longer loads the theme-rule generator on first load when its build keeps whole modules or every re-export: Next.js with Turbopack when the app also usesuseThemeelsewhere (for example through Toast), and hosts that lend each package entry whole to other bundles. A page that rendersThemestill loads the generator, becauseThemecompiles theme CSS at run time. Token resolution now reads the unset status-role defaults from a small module that the generator also reads, instead of importing the generator. The module that definesdefineThemeno longer re-exports the CSS generators;@astryxdesign/core/themeand@astryxdesign/corestill export them by the same names. Every resolved token and every generated rule stays the same. No API changes. - Thumbnail: focusing Open now shows one ring, on the image container, instead of a second ring on the button inside it.
- A relative
Timestampis now named by the words it shows, then the full date: "2 hours ago, March 25, 2026 at 10:00:00 AM Coordinated Universal Time". A button, link, or radio that contains it keeps its visible words in its name, so voice-control users can say what they see (WCAG 2.2 SC 2.5.3). A calleraria-labeloraria-labelledbystill names it instead. - A
Toastrendered on its own, outside aToastViewport, no longer holds a live role, so a screen reader does not read it a second time when its caller announces the message. Its text stays readable in browse mode. Only the viewport announces a toast; a caller that renders aToaston its own owns its announcement. Reported by: - ToggleButtonGroup wraps onto more rows when it is wider than its container, instead of shrinking its buttons until their labels are cut. Each row keeps its own button ends and keyboard order is unchanged; only a single button wider than the whole container still shortens its label. A group that fits looks the same as before.
- A clickable
Tokenpasses a caller'saria-pressedto its inner button, so a filter chip can expose a pressed toggle to screen readers. Before,aria-pressedlanded on the outer container, which has no role, and assistive technology ignored it. - Tokenizer: with
tokenOverflowBehavior="unfocusedLayer", keyboard users can now Tab to the collapsed field. Its placeholder takes the tab stop and opens the field with focus in the input, even when it holds no tokens. A disabled field keeps that stop, says it is disabled, shows itsdisabledMessage, and opens nothing; no element is natively disabled. - Tokenizer shows the caret in a focused, empty input when the field has no width
- An
OverflowListplaced directly in a horizontalToolbar'sstartContentnow folds its actions into its overflow trigger besideendContent, instead of pushing the end content past the toolbar's edge. A single-rowOverflowListin a flex row now unfolds again when the row widens, and never shrinks below its folded width, so a squeezed row keeps its trigger whole. In a flex row its own width is its unfolded items, at most the row's width, so a folded list keeps the width the row gives it and content after it sits after that width. In a block parent it fills the line, as before. A caller'swidth,max-width, or flex basis still sets it. - A Toolbar with start and end content wraps when the two do not fit one row: the end content moves to the next line instead of squeezing the start content until its title wraps and its badge is cut. Each side keeps its controls on one line while it fits the toolbar's width, and a toolbar that fits its container looks the same as before. The kanban board template's header now fits a phone.
- Tooltip paints the theme's inverted surface (
--color-background-inverted), the surface Toast paints, instead of the primary text color, so a theme that sets its inverted surface styles tooltips and toasts alike. Its text stays the page surface color. To keep the previous look, a theme can set thetooltiptarget'sbackgroundColortovar(--color-text-primary). - A
Tooltipno longer opens when an app moves focus by script to its trigger right after a mouse click or a tap that focused nothing, such as a click on page text. The last input was a pointer, so the focus is not keyboard focus. A text-field trigger still opens, as browsers mark a pointer's focus on a text field:focus-visible, and focus after a key press still opens the tooltip. - Tokenizer, Typeahead and PowerSearch draw the on-field status icon, as TextInput does. With
statusVariant="tooltip"the icon is a button that shows the status message on hover, keyboard focus or a tap; before, sighted people saw only the border tint and never the message. In the sheet presentation a tap on the plain icon opens the sheet, as a tap on the tokens does. WithtokenOverflowBehavior="unfocusedLayer", the icon shows once the field opens. AppShell: on a phone, when the theme keeps the standard width points, a server-rendered page no longer paints the top navigation's full row of links for a moment while its script loads; the bar shows only its heading and end content. The menu toggle still arrives with the script.- On a phone, TopNav's compact bar keeps a plain-text heading on one line and ends it in an ellipsis, so a long title no longer wraps and makes the bar taller.
- TopNavMenu and TopNavMegaMenu close when you pick an item with the keyboard, a finger or a pen, and return focus to their trigger. Before, the menu or panel stayed open with focus inside it. In a mega menu, following the featured card's link this way closes the panel too. A mouse or trackpad pick leaves the menu open, as before. To keep a menu open after a pick, set the item's
hasCloseOnSelecttofalse. - On a phone, TopNav's end content is never wider than the bar, so an end item that can narrow, like a search field, narrows and the menu button stays in view. The Shell Nav template's search now narrows on a phone instead of pushing the menu button off screen at 375 px.
- A TreeList row with no action (no onClick, href or children) now shows the focus ring when it has keyboard focus. Such a row was already a stop in the tree's arrow-key focus, but it showed no sign of focus.
- Type-to-select: a letter typed with AltGr on Windows, such as ł on a Polish keyboard, now selects a matching item, so typing ł in a Selector reaches "Łódź". AltGr reports Control as well, and type-to-select treated it as a Control shortcut and dropped the letter. This covers
useTypeaheadand every collection that uses it (Selector, MultiSelector, DropdownMenu, ContextMenu), a searchable Selector's typed-to-open query, and TreeList. Control and Command shortcuts such as Control+L still do not type-select. Reported by Rajatendu1. - Typeahead and Tokenizer: when a search matches more items than
maxMenuItemsshows, the result count announced to screen readers names every match, not only the rows shown. - The useHotkeys docs no longer recommend
shift+/for a help overlay. The hook compares the final key againstevent.key, and Shift+/ produces?on US layouts, so ashift+/registration never fires there. The docs now use?and say to register a punctuation key that shift changes as the character it produces. No behavior changes.
Performance
- CheckboxInput runs its disabled-message tooltip only while that message can show (the checkbox is disabled and has a
disabledMessage), so a page of many checkboxes renders faster. A disabled checkbox's reason now also describes it in the server-rendered HTML, before the page hydrates. - A pointer
ContextMenu(the default presentation, and every Table cell menu) no longer carries the touch sheet's action list:ContextMenunow sharesDropdownMenu's sheet module, which loads the sheet only for the sheet presentation. A page with a Table that has cell actions, or with aContextMenu, loads about 57 KB less JavaScript before first paint (about 20 KB gzip). A menu withpresentation="bottom-sheet", oradaptiveon a compact touch screen, still loads its sheet after mount and opens it as before. - Reading the locale or direction with
useLocale,useDirectionoruseCollatorno longer loads the message parser:useLocalealone bundles to 441 bytes gzip instead of 10,250. A page that translates any Astryx string still loads the parser, as before. Translation output, with or without a provider, is unchanged for copies of one Core version. OverflowLists that mount or change in one render now measure together after it, before the frame paints. When other components write to the page in the same render, each list used to read its size after those writes and force its own layout; now all lists read their sizes first and the page lays out once for them. The first painted frame is the same.useOverflowresults andonOverflowChangearrive one microtask after the render instead of inside it. A test that checks them right after a synchronous render awaits that microtask first, for example withawait act(async () => {}). With fake timers that also fakequeueMicrotask, as Jest's modern fake timers do by default, flush the faked microtasks too, for example withjest.runAllTicks()orvi.runAllTicks().- Importing
ResizeHandleon its own no longer pulls inuseResizableand its resize controller. The handle reads the hook's collapse, release and maximum details from the resize model instead, so its static import graph drops from 90 to 84 modules. A bundler that tree-shakes already dropped most of that code (25 bytes gzip less); one that keeps whole modules loads the controller only with the hook. Switchno longer measures its track when it mounts. It reads the track's size at the first press instead, so a settings page with hundreds of switches renders without one forced layout per switch. Dragging, right-to-left layouts and a press right after mount work as before. Two small differences: a mouse or pen drag after a toggle now flips at the thumb's current size (up to 4 px different at the medium size), and a theme that resizes the Switch thumb animates its first value change from the default size.- A page whose components bring no tooltip code, such as one that renders only
TextandHeading, loads about 9.6 KB less JavaScript before first paint (about 3.4 KB gzip). The truncation tooltip's tap handling no longer shares a file with the touch trigger code that its lazily loaded tooltip uses, so that code stays with the tooltip. Tapping a truncated text opens its tooltip as before. - Text: a truncation measurement that finds the same result no longer schedules a state update, so a page that mounts many truncating texts at once, such as a wide windowed Table, does less work.
useTruncationreturns the same values as before.
Documentation
- The agent docs
astryx initwrites, and the computer-level skill, name the Astryx prop names that differ from other libraries in the workflow's third step: buttons, badges, tokens and tabs take their text inlabel(Text, Heading and Link take children), booleans start withisorhas, and every input takesvalueandonChange. An agent that writes props before it reads a component now writes these right far more often. Runastryx upgradeorastryx initto refresh a project's agent docs. - BottomSheet's docs say that a modal sheet with no data-autofocus field opens with focus on its panel in Safari on iOS, as in Chromium, and that marking a field data-autofocus opens on it in every browser.
- Button's docs now list
refand say that in link mode (withhrefand not disabled) the ref receives the anchor (or the link component's element), although its type namesHTMLButtonElement. No runtime or type change. - CheckboxListItem and ListItem docs say that a string
descriptionshows on one line with an ellipsis, and that a node such as<Text type="supporting">shows the full text on more lines. - The agent workflow copy that Core ships says to read a block example for a part the template lacks, not to insert a block, matching
astryx build. - The docs of four components list props they already take and left out: ComplexSelector's
isLabelHidden,description,labelTooltip,isOptionalandisRequired; Selector'schangeAction,labelTooltip,placementandisDefaultOpen; Toast'sisExiting; and ContextMenuItem'sonClick,href,target,rel,isDisabled,hasCloseOnSelect,variantandref, which it takes as the DropdownMenuItem it re-exports. - The README's setup box now shows how to install the CLI at the version of
@astryxdesign/coreyou have, saved exactly whenpackage.jsonpins Core exactly, and its link to the Astryx CLI section now works. A second box tells agents to ask the Astryx CLI before they write code, with three commands that work with or without the install:build,componentanddoctor --built .. Before, the setup box's command installed the newest CLI with a^range. - The README's stylesheet setup boxes (Next.js, Next.js + Tailwind, Next.js + StyleX) now import the theme's
fonts.css, asastryx theme adddoes. It holds@font-facerules for the font files the theme package ships, so the page requests nothing outside the app. Before, a page set up from those boxes loaded no theme font and fell back to the system font stack. - The typography docs say what Core builds, in one rule: a heading with no
familytakes the body's whole font list; with its ownfamily, only its ownfallbacks;fallbackswith nofamilybuild nothing.TypographyConfig, itsheadingfield,defineTheme'stypography, thefonts-and-assetsdoc page and the theme template say it; thefont-setuppage says a heading with no family uses the body's and points tofonts-and-assetsfor the rest. - Dialog's guidance now names its one nesting exception: an AlertDialog that confirms a destructive action may open from a dialog. It asks one question, and Escape closes only the alert.
- Text's
asdocs listh1,h2andh3, and PowerSearch'sstatusVariantdocs listtooltip, as their types already allow; thetooltiptext says what PowerSearch shows for it. - Grid's docs say that
columns={{minWidth}}alone keeps each column at its track width, so a grid with fewer items than tracks keeps an empty column, and thatrepeat: 'fit', or amaxno more than the item count, lets the items grow to fill the row. - Hook docs for
useChatDictation, soastryx hook useChatDictationandastryx searchreturn it, and auseChatDictation — Voice inputexample block: a start and stop control that stays off when the browser has no speech recognition. - Hook docs for
useChatPasteAsToken, soastryx hook useChatPasteAsTokenandastryx searchreturn it, and auseChatPasteAsToken — Long pasteexample block: a composer that uses a threshold of 40 and a Pasted note label. - Hook docs for
useSpeechRecognition, soastryx hook useSpeechRecognitionandastryx searchreturn it, and auseSpeechRecognition — Transcriptexample block: a headless control that shows whether the browser can listen and the interim transcript. - Hook docs for
useSyntaxTheme, soastryx hook useSyntaxThemeandastryx searchreturn it, and auseSyntaxTheme — Keyword colorexample block: the word const painted with the keyword color of the GitHub Light syntax theme. - The
InternationalizationProviderexample that changes one Astryx string is titled for a change across the app, not a change to one component. - Docs now answer three questions in the first sentence that agents read:
- Icon props such as TextInput
startIcon, SelectorstartIcon, FieldlabelIcon, DropdownMenuItemiconand SideNavItemicontake a semantic icon name such as'search'(seeastryx docs icons), an icon component, or an icon element. Their documented type is nowReactNode | IconType, as in the code. - Selector
valueandonChangeshow thehasCleartypes: withhasClear,valueis required andstring | null, andonChangereceivesnullwhen the user clears the selection. - useTableSelectionState names what it returns:
selectionConfigandselectionStatewithselectedKeys,selectedCount,hasSelectionandclearSelection, with a bulk-action example.
No API or behavior changes. - Icon props such as TextInput
- Markdown's anatomy now says when its Image part shows alternative text: for an empty image URL, while an unsafe URL renders as source text. Its guidance adds two don'ts: plugins cannot cross a Server Component boundary, and Markdown does not sanitize renderer output. Prop docs now describe
density,isStreaming,onLinkClick, andcomponents;inlinePluginskeeps its own description instead of lending it toplugins;contentWidthnames its 680 default; and thecontentAlign="start"description now says inline start instead of left. TheonLinkClickdocs say that a customlinkrenderer does not receive the handler. - MetadataListItem's prop docs now list
xstyle,className,style,ref, anddata-testid, and say which element each one reaches: the labeldtwhen the item is side by side, or the wrapper when it is stacked. Thedata-testiddocs say that a side-by-side item puts-labeland-valueon its two cells. - MobileNav's prop docs now list
label,xstyle,className,style,ref, anddata-testid, and thelabeldocs say what names the drawer when it is not set. MobileNav's Chinese and dense prop text now reaches the docs: it was written where the doc compiler does not read it for a doc with two components, so those docs showed the English text. The Chinese text no longer marksisOpenandonOpenChangeas required; inside AppShell the drawer reads them from context. - MobileNavToggle's docs now say every case where it renders nothing: above the mobile breakpoint, without an AppShell mobile context (AppShell's, or an
AppShellMobileContextyou provide), and when AppShell has no mobile navigation (no side or top nav,mobileNav={false}, or amobileNavnode). - MoreMenu's prop docs now list
isMenuOpenand say that withoutsizethe trigger takes the surrounding size (from a SizeProvider, ButtonGroup, or Toolbar), elsemd. The Chinese docs gainisMenuOpenandonOpenChangeand the note on where hostdata-*attributes land. - NavHeadingMenu's docs now document NavHeadingMenuItem and its props (
label,description,icon,href,onClick,isDisabled,ref,xstyle), addrefto the menu, and say thatminWidthwins over the size's minimum width. New best practices name the WAI-ARIA menu pattern and its keys, say to name a standalone menu, and explain how a disabled row stays reachable. - The npm descriptions of
@astryxdesign/coreand@astryxdesign/cliname Astryx, so a search for "astryx" on npm lists them with the other Astryx packages. - The README's Quick Start now installs the CLI and runs
initas part of setup, and the note at the top says setup is install, theninit, run once before writing UI, and says whatinitprints and writes. Before, Quick Start installed only Core, a theme, and StyleX, and the note framedinitas an extra for AI agents, so agents that followed the README finished setup without the Astryx guide inAGENTS.md. The repository README's Getting Started gets the sameinitstep. - The useTableSortable doc now says in its first sentence that the plugin adds the header sort controls but does not reorder the rows, and shows two ways to sort the data: from the sort state yourself, or with useTableSortableState. It also says a column needs
sortableto get a control, and gives the correct default ofallowUnsortedState(true). No API or behavior changes. - The useTableSortableState docs say that arrays and plain objects have no sort text, so they need a comparator, and that a Date sorts by its time and an Invalid Date sorts with the missing values. A new useTableSortable example sorts by a status rank and a tags array. Table's
columnsprop says Table has no onRowClick prop: to open a row, put a Link or Button in its main cell's renderCell. No API or behavior changes. - Table's docs say how a long token, such as a code identifier or a URL, wraps in a data-driven table: the columns you pass in
columnsare sized from their definitions, not their content, so a token wider than its column breaks inside the token. To keep tokens whole, give the column a floor that fits them withproportional(1, {minWidth})orpixel(), or compose the table in children mode, whose columns follow their content. - Table documents its
emptyStateprop, how to open a row from a link or button in its main cell (Table has no row-click prop), and what a customTablePlugincan change, in which order. - useTableFiltering documents its required
searchConfigand shows that you filter the rows yourself, with an empty state for no matches; useTableFilterState namesclearAll. - useTableSelection explains how
getIsItemSelectable(no checkbox) differs fromgetIsItemEnabled(a disabled checkbox) and what select-all does with each. - useToast lists every
ToastOptionsfield with its default, and says it returns the show function itself (const showToast = useToast()), not an object.
No API or behavior changes.- Table documents its
- The Toast doc now says in its first sentence that
useToast()needs no provider or mounted ToastViewport. The Table hooks whose config does not mention the row type (useTableSortable, useTablePagination, useTableFiltering, useTableColumnSettings, useTableColumnResize, useTableInfiniteScroll, useTableStickyColumns) now say thatTis the row type, that TypeScript cannot infer it and falls back toRecord<string, unknown>, and that you pass it, as inuseTableSortable<Walk>(…). Their examples are typed. No API or behavior changes.
Other Changes
- Internal: Core's internal touch entry re-exports its group press tracking and group-item mark for Lab's Rating, and the catalog gains two Rating messages. Apps import nothing new.
- Internal: the swipe hook's and the swipe layer's file headers keep only their tags and the SYNC reminder. The prose that explains each moves, unchanged, into the JSDoc of
useSwipeActionandSwipeActionsLayer. No behavior or type changes, and neither is exported from the package entry point. - Internal: the swipe's shared drag lists the committed options ref that its begin check reads. The ref is stable, so a row keeps one drag for its life. Not exported from the package entry point.
- Internal: the UIKit values of a swipe-action row (the swipe threshold, the springs a confirmed row runs ahead on and a released row settles with, the touch claim distance the web needs) and the release rule that picks closed, open or fire (a fast release goes the way it moves, a slow one by where it is, and only a confirmed full swipe fires), checked against releases measured on UIKit. Not exported from the package entry point.
Contributors
Thanks to everyone who contributed to this release:
0.7.16
Experimental APIs
New Features
- NumberInput takes
entryErrorBehavior, so a form can pass one value to all of its date, time, and number fields. A typed number is complete only at Enter or blur, so both values keep NumberInput's current timing: its rejection,aria-invalid, announcement, andonEntryErrorChangereport appear at Enter or blur, never while a person types. Setting the prop, or FormLayout'sdefaultEntryErrorBehavior, changes nothing a person sees in a NumberInput. Pagination's page box passes'complete', so a FormLayout around it never changes it. (#11492) - DateInput, DateTimeInput, and TimeInput take
entryErrorBehavior, and FormLayout takesdefaultEntryErrorBehavior. The prop sets when a field shows its own entry error, such as a date the calendar does not have or a time outsideminandmax. It does not set when validation runs, and it is not React Aria'svalidationBehavior.'complete', the default, keeps each field's current timing.'blur-or-enter'holds the message,aria-invalid, the invalid styling, the announcement, and theonEntryErrorChangereport until the person presses Enter or leaves the field; an edit that makes the entry valid or empty still clears the error at once. A field's own prop wins over the form default, a nested FormLayout replaces it, and a Dialog opened from the form starts without it. PowerSearch value editors and Table filter editors keep'complete'. The newEntryErrorBehaviortype names the two values. (#11485) - A Lightbox gallery's caption sits in a band two lines tall under every photo, so the photo keeps one size and place from item to item. A photo with no caption keeps the band's space without its backing. A longer caption shows two lines, the second ending in an inline "more" link, which opens the whole caption over the photo. The whole caption is always the viewer's accessible description. (#9810)
The viewer is a media surface: its controls, caption and counter take the theme's dark surface tokens through
MediaTheme. The caption is bodyTextwhose lines start at one edge, "more" and "less" areLink's button form in the caption's own type, and the band clears the screen's bottom edge and its safe area. A gallery's caption sits on a backing that keeps it at 4.5:1 over any photo. A tap that opens the viewer paints no focus ring on its first control, and paging from a focused "more" or "less" keeps focus in the viewer. - NumberInput:
onEntryErrorChangereports why the field rejects typed text, so an app can word its own message. It receives aNumberInputEntryErrorwith akindthat does not depend on the locale (unreadable,fractionalfor a fraction whenisIntegerOnly, oroutOfRangefor any number whileminis abovemax), the typedtext, and, forfractionalandoutOfRange, the number asvalue. It runs each time the rejection changes: at Enter or blur, when an edit makes the text valid or empty, when a newvalue,min,max, orisIntegerOnlychanges or ends it, and when disabling the field drops the text. It reportsnullwhen the rejection ends, or when the field unmounts while one stands, and never twice for the same rejection. Pass anerrorstatuswith a message to word the rejection; that message is the one announced. (#11415) - New message
@astryx.richTextEditor.link.urlPlaceholder("example.com"), the placeholder of the RichText toolbar's link field. The descriptions of the other@astryx.richTextEditor.link.*messages and@astryx.richTextEditor.toolbar.linknow describe the link popover that replaces the link dialog; their messages are unchanged. (#8717) - Column windowing keeps focus and place: with
useTableColumnsVirtualization, a focused cell whose column scrolls out of the window stays mounted with its original element until focus leaves the table, moves to another cell, or its column is removed, when focus returns to the Table's scroll area. Focus in a menu that a cell opens keeps the cell's column too. Changing column order, widths, visibility or pinning keeps the first visible column and how far it is scrolled. Tables that do not opt in are unchanged. (#11018) - Tables can window their columns: pass
useTableColumnsVirtualization({initialViewportWidth})toTable.virtualization. Table keeps every column definition and width, mounts only the unpinned columns near the inline viewport plus two overscan columns per side, keeps pinned columns mounted, and gives mounted cells full-tablearia-colindexvalues witharia-colcounton the table. When the scroll area is at least as wide as the table's minimum width, every column mounts.Table.virtualizationalso accepts a list with at most one rows and one columns capability. Unsupported content or structure renders every column with a development warning. Adding or removing the columns capability remounts the table. Tables that do not opt in render as before; their Table import carries about 0.5 KB gzip of column windowing wiring, and the column planner loads only with the hook. (#11014) - Add Table infinite loading with
useTableInfiniteScroll({hasMore, isLoading, onLoadMore}). One Promise request latch coordinates automatic and manual loading, failures pause automatic retry, and the persistent busy Button owns progress announcements and focus continuity. (#10570) - Tables can window rows and columns together: pass both
useTableRowsVirtualizationanduseTableColumnsVirtualizationtoTable.virtualizationas a list. Table mounts only the cells near the viewport on both axes, keeps full-tablearia-rowindexandaria-colindexvalues, and keeps a focused cell's row and column mounted while either scrolls away. Tables that do not opt in are unchanged. (#11019) - TextArea
htmlMaxLengthsets the nativemaxlengthattribute, so a form can cap typing in UTF-16 code units, including an SSR form before hydration. It is independent ofmaxLength, the soft counter, which still counts user-perceived characters and never blocks typing. TextArea adds no truncation or validation of its own, and renders no nativemaxlengthwhenhtmlMaxLengthis unset. (#11295) - TimeInput:
onEntryErrorChangereports why the field rejects typed text, so an app can word its own message. It receives aTimeInputEntryErrorwith akindthat does not depend on the locale (unreadable, oroutOfRangefor a time beforeminor aftermax), the typedtext, and, foroutOfRange, the ISO timevalue. It runs each time the shown rejection changes, including when a newmin,max, orvalue, or disabling the field, changes it, never twice for the same rejection, and withnullwhen the rejection ends or the field unmounts while it stands. The native and bottom-sheet surfaces take no typed text, so they never report. (#11413) useTruncationtakesisExpanded: pass true while the text is shown in full; the hook keeps reporting whether it is cut off when clamped. A Lightbox caption uses it, so its "less" stays while the caption is open. (#9810)
Fixes
- AppShell keeps server-rendered content when a screen is narrower than the server assumed. On a phone, the shell learned its mobile layout in an urgent update right after it hydrated. When the content inside the shell had not hydrated yet, because its code streams in or loads later, React rendered that content again in place of its server HTML: a visitor lost scroll position and focus, and images inside loaded twice. The shell now takes the client's breakpoint answer in a transition, which waits for that content to hydrate. A client-rendered app and a correct
mobileNav.defaultIsMobilehint behave as before. No API changes. (#11441) - BottomSheet syncs its focus return target at commit, and no longer copies its stack view during render. A sheet removed after a render React discards, as a suspended transition does, returns focus to its committed
finalFocusRef. (#10918) - BottomSheet: when a touch flick closes a sheet, the dim behind it now clears in step with the sheet. Before, the sheet was gone in about a tenth of a second while the dim was still mostly there, and it kept fading for over half a second more. The fade now follows the close spring's own progress. Reduced motion and every other close are unchanged. (#11400)
- BottomSheet keeps its snap points and its reactivated entrance in state, and syncs its drag's stop resolver at commit. A render React discards that changes
snapPoints, as a suspended transition can, no longer changes the stop a released drag rests at. (#10873) - ChatComposerInput: an empty input keeps its one-line height and takes typing after a page restyle, for example after an open Dialog that holds a SegmentedControl unmounts. Before, its editable area could collapse to 0px, so a click landed beside it and typing did nothing until a reload. (#11428)
- useContainerReveal keeps revealed content always visible only when the primary pointer is coarse (a phone or tablet). A touchscreen laptop used with a mouse or trackpad now reveals on hover and keyboard focus like any other mouse device. Previously any touchscreen kept the content visible at rest, so a Thumbnail's hover remove button, Markdown heading links, and every app's hover-revealed row actions never hid. (#11218)
- A theme's padding written with
clamp(),calc(),min(),max()orvar()with a fallback now builds as written. The theme compiler splitspadding,paddingBlockandpaddingInlineon the spaces between values only, never on a space inside parentheses or quotes, sopadding: clamp(8px, 2vw, 16px)stays one value instead of becoming broken CSS. No API changes. (#11347) - DateInput, DateTimeInput: a
valuethat the app passes at an Enter or blur that keeps a rejected date no longer erases it, so the entry meets WCAG 2.2 3.3.1 (Error Identification). Before, when an app setvaluein the same update as an Enter or blur that kept unreadable, incomplete, nonexistent, or out-of-range date text, as an app does when it restores the date it had before the edit, the field dropped the text, its message, andaria-invalid, and reportednullthroughonEntryErrorChange; a native date control lost its rejection message the same way. Now the text, its rejection, and its message stay at every such Enter or blur, a blur after an Enter included, so the person can correct the entry, and nothing is reported. A later newvaluereplaces the text, as before. No app code changes are needed. (#11470) - DateInput, DateTimeInput: in a standalone field, rejected dates now meet WCAG 2.2 1.4.1 (Use of Color) and 3.3.1 (Error Identification); inside an InputGroup they set
aria-invalidand are announced. Before, text that is not a date was marked invalid and announced on every keystroke, with no visible message, and Enter or blur reverted it. A native date control flagged each partial year while the year was typed, showed no message, and dropped the rejection when it restored the committed date at blur. Now text that is not a date shows nothing while you type; Enter or blur keeps it in the field and shows "Invalid date" as the field's error status, witharia-invalidand one announcement. Its message replaces a callerstatus, as the field's other rejections already do; withonEntryErrorChange, a callererrorstatus with a message still wins. A native date control's rejection waits for Enter or blur, shows the out-of-range message a typed date shows, under the samestatusrules, and stays shown after the control restores the committed date at blur. A shown rejection stays through an edit that leaves the date wrong or unfinished, and clears once the date is valid or empty. What a form posts does not change: while kept text is not a date, a hidden input posts the committed date under the field'sname, and the next Enter submits the form. (#11407) - SideNav, TopNav, Breadcrumbs: a Ctrl-, Cmd-, Shift- or Alt-click on a link in the mobile navigation drawer opens it the way the browser decides, a new tab for instance, and leaves the drawer open. A plain click still closes it, and so does a modified click that the row's own
onClickcancels, since nothing opens elsewhere. (#8979) (#9390) - DropdownMenu syncs the refs its show and hide call at commit. After a render React discards, as a suspended transition does, its entrance under a finger holds input as the committed menu says. (#10905)
- In forced-colors mode (Windows contrast themes),
primaryandsecondaryButtons gain aButtonTextborder, anddestructivekeeps itsCanvasTextborder; in a connectedButtonGroupthe solid buttons keep the group's dividers and close the group's outer edge, with no doubled seam. Floating surfaces that separate from the page with a box shadow alone gain aCanvasTextborder:Popoverand every surfaceusePopoverpaints (includingDropdownMenu),DropdownMenuSubMenuflyouts,ContextMenu, and anisInlineDialog. Forced colors removes fills and box shadows, which left these controls and surfaces without an edge. The borders exist only in forced colors, so nothing changes elsewhere. A theme that sets a solid variant's own border width keeps it, so Gothic'ssecondaryButton stays borderless. (#7677) - A layer with several triggers now opens at another trigger when the press on that trigger is the one that closes it, with a mouse or a finger. A press on the open trigger still closes it. (#11337)
- An anchored layer flush against its trigger, or over its edge, no longer slides over it: its entrance scales in place, as it does for a layer over its trigger's center. A menu at the pointer still slides from the side it lands on. (#11417)
- An anchored layer that has room to its trigger no longer starts its entrance over it: its first step toward the trigger stops at that room. So a tall tooltip 4 px beside its trigger no longer covers it on its first frame in Safari. (#11396)
- The layer runtime syncs its close-start and replayed-show refs at commit, not during render, and its keep-open press reads the committed open state or the shown layer. A render React discards no longer leaves its values for later callbacks. (#10912)
- A light-dismiss layer opened while a press is released no longer closes at that release. A DropdownMenu or ContextMenu row that opens a Popover when chosen with a mouse now leaves it open, as it already did with a finger; the next press outside, or Escape, closes it as before. (#11258)
- A mouse click on the dark space beside a Lightbox photo now closes the viewer. Before, the viewer stayed open after a click there within the photo's natural width, or within a wider caption's width. (#11354)
- A single photo's caption in a
Lightboxnow shows as a gallery's does. It sits in the band at the bottom of the viewer, on the caption's backing, which keeps 4.5:1 over any page behind it. The photo centres above it. A caption longer than two lines ends in "more", which opens it in full over the photo. A single photo with no caption shows no band. (#10284) - When a reorderable
Listrow does not render again, its handle's name still follows it. A handle named after its place ("Reorder item N") follows that place when rows above it go or the rows reorder. A label that gains or loses its text renames the handle. (#10815) - DropdownMenu, ContextMenu, Selector, TabList, TopNav, SideNav, Breadcrumbs: when a finger picks a menu row, the click guard cancels only that finger's
touchendonce the menu has named the touch, so another finger'stouchendpasses. The menu names the touch from thetouchstartthat follows itspointerdown. AtouchendwithoutchangedTouches, or a lift whose touch the menu could not name, keeps the old rule: the nexttouchendis cancelled. (#11164) - MoreMenu, InfoTip, PowerSearch (with its PowerSearchToken and PowerSearchFilterEditor defaults), Toast, and InputClearButton now pass host
data-*attributes to their own element, as other components do: the trigger button for MoreMenu and InfoTip, the primary control for PowerSearch, the token and editor root for the PowerSearch defaults, the toast element for Toast, and the button for InputClearButton. Component-owned attributes stay with the component. A new test renders every exported component that renders an element of its own with adata-*attribute, and fails when the attribute does not reach the DOM. (#11406) - NumberInput: a rejected entry now shows a message and stays in the field, so the field meets WCAG 2.2 1.4.1 (Use of Color) and 3.3.1 (Error Identification). Before, every draft that was not an accepted number, an unfinished one such as
-included, setaria-invalidand was announced on each keystroke, while the text only turned secondary; blur then reverted a draft that did not parse, with no message. Now nothing is marked or announced while a person types, because a typed number is complete only at Enter or blur. At Enter or blur, text that is not a number, a fraction whenisIntegerOnly, or any number whileminis abovemaxstays in the field: the field shows "Invalid number" as its error status, tied to the input byaria-describedby, setsaria-invalid, and announces it once. Inside an InputGroup the rejection setsaria-invalidand is announced. An edit that makes the draft valid or empty clears it at once. A number outside an ordinary range still clamps and commits throughonChange. A callererrorstatus with a message still shows in place of the field's message; awarningorsuccessstatus no longer hides a rejection. What a form posts does not change: while blur keeps a rejected draft, a hidden input posts the committed number as the field showed it before. Pagination'sinputvariant shows the message on its page box's status icon and widens the box beside the typed text while a rejected entry stays, so the bar keeps its height. No app code changes are needed. (#11415) - Under a finger, a Popover that overlaps its trigger now grows from where it meets the trigger, as the pointer entrance does. A popover a few pixels over its trigger's side grows from that side, not from below. A popover over its trigger's center grows from that center by scale only. Every other landing grows as before. (#10949)
- Toast announces the rendered message when a body's text comes only from a component, and from custom layouts (#7853) (#11175)
- SegmentedControl: where the control has no layout, as in a unit test's DOM, a click on a later segment keeps that segment selected instead of switching to the first segment a moment later. Browsers are unaffected. (#11487)
- Selector's presentation syncs its show, hide and popover-content refs at commit. After a render React discards, as a suspended transition does, opening the popover runs the committed show. (#10917)
- Slider syncs its values, change-end callback and touch update refs at commit. After a render React discards, as a suspended transition does, a press on the track reports the committed value to the committed
onChangeEnd, and a finger dragging a thumb reports to the committedonChange. (#10913) - Table:
useTableSortableStatecalls theonSortChangeof the last committed render. Before, a sort click during a transition that had not committed yet called the callback from that pending render. (#11433) - TimeInput, DateTimeInput: a rejected typed time now meets WCAG 2.2 1.4.1 (Use of Color) and 3.3.1 (Error Identification). Before, every draft that was not an accepted time, an unfinished one such as
1included, was marked invalid and announced on each keystroke, shown only as secondary-color text, and blur reverted it with no message; a native time edit outsideminormaxshowed no message and its rejection cleared at blur. Now an unfinished time is never flagged: a time outsideminormaxshows once it is complete (its hours, both minute digits, both second digits when the field shows seconds, and in 12-hour text its day period unless the hour reads 0 or 13–23), and text that is not a time shows at Enter or blur. The rejected text stays in the field, and a standalone field shows the "Invalid time" message as its error status, witharia-invalidand one announcement; inside an InputGroup the rejection setsaria-invalidand is announced. Enter in TimeInput and in DateTimeInput's time field commits the typed time and still submits a surrounding form; in DateTimeInput's open preset-time list, Enter picks a time as before. A native time control restores the committed time at blur and keeps its rejection shown. A callererrorstatus with a message still shows over the field's message, and the rejection is announced once; awarningorsuccessstatus no longer hides a rejection. In DateTimeInput, a date rejection's message comes first and a time rejection under it is announced. What a form posts does not change: while blur keeps a rejected TimeInput draft, a hidden input carries the field'snamewith the committed time. (#11413) TimeInputandDateTimeInput: a bound with no whole minute inside the range keeps its own seconds, so the clamp stays inside the range. Before,clampTime('12:00','23:59:30')answered23:59— below the minimum the caller set. In aTimeInputsheet a wheel rest past such a bound committed nothing; in aDateTimeInputsheet, changing the date onto such a bound committed the out-of-range23:59. (#10159) (#10159)- Tooltip's and HoverCard's touch trigger, and Tooltip's handlers with the controlled and enabled flags they carry, sync at commit. After a render React discards, as a suspended transition does, a tap answers with the committed props, and a press outside still closes a shown tooltip. (#10892)
Performance
- Markdown text transforms that declare
requiredSubstringslook for those substrings in one pass over the source. Before, each paragraph searched the rest of the document again, so long Markdown (such as a long streamed chat answer) rendered more slowly with each paragraph. Output is unchanged. (#11403)
Documentation
- The docs playgrounds for TextInput, TextArea, NumberInput, CheckboxInput, Switch, ProgressBar and StatusDot open with realistic values instead of prop-name placeholders, the Heading playground opens as a level-1 heading instead of inheriting Text's sample with
type: 'body', and the ButtonGroup, TabList, SegmentedControl and TopNav playgrounds open with named sample items instead of numbered ones. (#11351) - Hook docs for
useOutlineFromDOM, soastryx hook useOutlineFromDOMandastryx searchreturn it, and auseOutlineFromDOM — Articleexample block: an article and an Outline built from its headings through the hook, with a button that adds a section and its linked entry. (#11234) - ListItem's
startContentandendContentdocs now say that the content sits inside the row, before the label or after the label and description, not before or after the item. (#11336) - MetadataList's guidance now says that assistive technology reads each label with its value, and that the title does not name the list or add a heading. Its prop docs now list
classNameandstyle, and thelabeldocs say thatposition: 'start'places a label at the inline start of its value, not on the left. (#11391)
Contributors
Thanks to everyone who contributed to this release:
0.7.15
New Features
- DateInput, DateTimeInput:
onEntryErrorChangereports why the field rejects typed text, so an app can word its own message. It receives aDateInputEntryError(exported from both components) with akindthat does not depend on the locale (unreadable,incomplete,nonexistent,outOfRangefor a date beforeminor aftermax, orunavailablefor a day thatdateConstraintsrules out), the typedtext, and, foroutOfRangeandunavailable, the Gregorian ISOdate. It runs each time the rejection changes, including when a newmin,max,dateConstraints, orvalue, a calendar pick, disabling the field, or Enter or blur changes it, and withnullwhen the rejection ends, or when the typed field leaves while its rejection stands, as when a presentation or pointer change shows the native or touch picker. With the callback, anerrorstatusthat has a message is the message the field shows and announces, and the field's own message applies only without one; awarningorsuccessstatus never replaces a rejection. When a rejection starts while that error message stays the same, the field announces the message once more for it. Without the callback, nothing else changes. For every DateTimeInput, while a native date control replaces the typed date field, kept typed text and its rejection wait for the typed field, so the field shows the caller'sstatusmeanwhile. The native and touch pickers take no typed text, so the callback never reports a rejection there. Fixes #10366. (#11311) - SegmentedControl: under a finger, pressing the selected segment lifts its surface as UIKit's does, and it settles back when the finger lets go. A pen lifts it the same way on a touch device. With a mouse on a desktop, or with Reduce Motion, nothing lifts. (#9724)
- Where the primary pointer is fine, a mouse press on a CheckboxInput or a RadioList option paints at once on
pointerdownand fades on release, as a finger's press does, instead of the browser's:active. A right click, or a press on a link or a button inside a RadioList option, does not paint the option. Other controls keep:activefor a mouse. (#8696)
Fixes
- Calendar, DateRangeInput: a two-month calendar whose
maxfalls in the month it would open on now opens with that month in the second pane. Before, withmaxset to today, or with a selected value starting inmax's month, it opened on that month and the next one, and every day of the next month was disabled while the previous month stayed hidden. The first pane still never goes beforemin's month, an explicitfocusDateis shown as given, and a one-month calendar is unchanged. (#11202) - Calendar: with
hasWeekNumbers, each row shows the ISO 8601 week number of its Thursday, the ISO week that holds most of its days. Before, most rows that start on Sunday or Saturday showed the previous ISO week, so the first two rows of a month could show the same number. Rows that start on Monday are unchanged. (#11271) - DateInput, DateTimeInput: a typed date that the calendar does not have, such as February 30, shows "Enter a real date". The message names the calendar, as in "Enter a real date (Persian Calendar)", only when the field's calendar differs from the
InternationalizationProvidercalendar. A day thatdateConstraintsrules out shows "Enter an available date". (#11309) - DateInput keeps its typed field's and native field's bookkeeping in state. A render React discards, as a suspended transition does, no longer drops typed text, clears a refused date, or reports the same date twice. (#10877)
- DateTimeInput keeps its native pickers' last value and commit epoch in state. A render React discards, as a suspended transition does, no longer drops a time chosen before the date, clears a refused date or time, or lets the same native edit commit twice. (#10861)
- Drawer keeps the side it exits to in state. A render React discards, as a suspended transition does, no longer changes the edge a closing drawer slides out to. (#10859)
- useLinkify and RichTextEditorAutoLinkPlugin: email detection now takes linear time. A long word with no email in it, such as a pasted hash or base64 string, no longer freezes the page for seconds. Valid email addresses link as before, with three exceptions. In the rich-text editor, an address directly after a period no longer links, and a quoted local part ends at the next quote. In useLinkify, a fragment glued to the end of an earlier address no longer links on its own. (#11306)
- Dialog, CommandPalette, BottomSheet, Lightbox, Drawer, MobileNav, Popover: a Tab pressed with Ctrl or Meta on the first or last control of a modal no longer moves focus to the other end, and the modal no longer cancels the press. A page or a host app that handles Ctrl+Tab or Meta+Tab itself, for example to switch its own tabs, now gets the press on every control, as it already did between the first and the last. Alt+Tab still wraps, because Safari moves focus to each item on Option+Tab. (#11247)
- Gestures in a same-origin iframe or a Picture-in-Picture window now time touches on that window's own clock. Before, a short tap there could start a long press, because the page's clock reads ahead of the window's. (#11155)
Item's swipe actions: underreveal, a fling opens the row at its actions; under either model a fling never fires an entry. On a side with two or more entries, only a drag that starts on the open row fires the outermost entry. The panel shows no entry's colour behind another. The entries fill it, and the entry that fires covers it until the row comes back or holds out. No API changes. (#11054)- Keep disabled Item actions focusable (#11169)
- After the window loses focus during a finger's press, lifting that finger no longer acts on any menu (DropdownMenu, MoreMenu, ContextMenu, Selector, and menus built on the public
useMenuPress), and a tap on a menu's trigger still opens it. Under a finger, a row lit by a press that is cancelled (a scroll, a second finger, the window losing focus) now clears, as on iOS. It clears in DropdownMenu and its sub-menus under anypresentation, MoreMenu, ContextMenu, Selector's list and the bottom sheet's action list, and in a menu built on the publicuseMenuPresswhose root can take focus. A mouse keeps its highlight. (#8508) - The menu press model behind DropdownMenu, ContextMenu and their submenus syncs its option, step and trigger-context refs at commit. A press after a render React discards, as a suspended transition does, now uses the committed options. (#10901)
- The mobile keyboard hook syncs its enabled, expanded and open flags at commit. After a render React discards, as a suspended transition does, a dismissal and the keyboard's listeners follow the committed options. (#10914)
- Outline's scroll spy reads its items, its
onActiveIdChangeand its active item as committed. A render React discards, as a suspended transition does, no longer changes which item a scroll marks or which callback a landed navigation calls. (#10802) - Carousel paging: a row that resizes while it settles no longer stops at once or runs back to an earlier page. The settle plays on at its speed, to the last page when it was heading there, and otherwise to the page nearest where it was heading. It ends on that page with no step when it goes back to native scrolling. A resize that leaves the row past its new last page, or that gives the row its first width, still lands it at once on the page it was heading for. (#10592)
- ResizeHandle reads its region, direction and disabled state as committed. A render React discards, as a suspended transition does, no longer makes a key press resize another region or refuse an enabled handle. (#10803)
- In a swizzled AppShell, the first Tab into the main region now stops on the region, as in the package's AppShell, when its first link or button sits inside a package scroll region that does not overflow (ScrollableArea, Table, CodeBlock, Tokenizer, BottomSheet), and the reverse. Arrow and Page keys are unchanged. No API changes. (#11225)
- A disabled
Stepnow reflectsdisabledon thestep-indicatortheming target, besidestep-label, so a theme can restyle a disabled step's indicator. In a compact horizontalStepperwith on-track indicators, where a disabled step's label is not shown, the indicator is the only target a theme can reach. Thestepandstep-descriptiontargets do not gain the selector. (#8997) (#9192) useStreamingTextkeeps where its reveal restarts in state. A render React discards, as a suspended transition does, no longer restarts a streaming reveal from the start or jumps it to the end. (#10862)- Table keeps one array for each list of columns, and for each list of plugins, compared by identity. A render React throws away, as a suspended transition does, can no longer replace the array the table last displayed. The next committed render reuses the array, so rows skip rendering when the columns and plugins match the committed ones.
useBaseTablePluginsalso keeps its array when the base plugins come in a new array of the same plugins. A column plugin with its own render-time cache, such as the tree plugin, still re-renders every row. (#10940) useTableSortableStatesorts only when its data, sort or locale changes. It re-sorted every row on every render of its owner. (#10942)- Table sorting with
useTableSortableStatecalls the latestonSortChange. Before, a sort header kept the handler from the last time the sort changed, so a parent that passed a new handler without a sort change had its old handler called, and that handler saw out-of-date state. (#11349) - Text and Heading: on Android, the first tap on a button or link inside truncated text opens the truncation tooltip, as on iOS. The tap focused the element first, and that focus took the tap; now only a keyboard focus counts. Tooltip: a tap on a text field inside a tooltip's trigger focuses the field and no longer opens or closes the tooltip. This includes a text field inside truncated text. (#11213)
- A Timestamp hover card's copy button now shows when the clipboard write fails, as CodeBlock's copy button does: the icon becomes a cross for 1.5 seconds, and the button is named, tooltipped and announces "Failed to copy value to clipboard." It used to do nothing. A theme that maps the
timestamp-copyslot keeps its rest glyph during a failure (copiedis false). The error itself is not shown. (#10434) - ToastViewport syncs its committed list at commit. A toast that only a render React discards showed, such as a suspended transition, reports no
onHidewhen a repeat replaces it and the same handler then dismisses it. (#10902) - Tokenizer's sheet numbers its searches and its opens in state. A render React discards, as a suspended transition does, no longer makes a reopen announce a search that never ran. (#10886)
- In Tokenizer's inline field on a touch screen (a tablet, or
presentation="popover"on a phone), removing a token with a finger no longer raises the touch keyboard. A tap on a token's own remove button (Token's ×) used to move focus to the field's input inside the tap, which makes iOS and Android show their keyboard; when the input was not focused before the tap (the keyboard was down), focus now stays where it was, unless the tapped × or another control in its token held focus, when focus moves to the input as before. A tap made while typing, a pen's tap, a mouse click, a key press on the remove button, and a remove control drawn by a customrenderTokenstill put focus in the input. PowerSearch's filter tokens, which render Token, get the same fix. (#8160)
Documentation
- Hook docs for
useThemeName, soastryx hook useThemeNameandastryx searchreturn it, and auseThemeName — Active themeexample block: the name of the theme wrapped around the caller. (#11235) - List's anatomy now names its optional header and drops a description part that List does not render. The
refdocs now say that the ref reaches the list element, with or without a header. (#11277) DefinedTheme.__componentIconsis now documented public API; its presence and shape follow the compatibility policy. (#11192)
Other Changes
- Internal: Core's internal touch entry re-exports UIKit's timing table and the motion engine's AnimateOptions and MotionHandle types for Lab's SearchField. Apps import nothing new. (#10956)
- Internal: the close button name of Lab's SearchField joins Core's message catalog. Apps import nothing new. (#10956)
- Internal: Core adds two internal hooks that keep a ref at the latest committed prop or callback for event and gesture callbacks, and an internal entry through which Lab reaches them. Outline's scroll spy, ResizeHandle and resizing logic, menu press handling, the mobile keyboard hook, and ToastViewport use them. Apps import nothing new. (#11352)
- Internal: one shared context request from a long press, a right click, or Shift+F10 and the context-menu key, reporting which input made it, one per gesture. A held finger's hold loses to a claim another gesture already made on that finger, and a control that keeps its press for a hold-repeat owns only its hold, so its right click and Shift+F10 still reach the request. A held pen's own context menu event is refused like a held finger's. The hold is UIKit's long press and requests as it begins. Not exported from the package entry point. (#8670)
- Internal: Core's internal layer hook drops a dismissal-check field that no component reads. The layer still refuses to reopen during the press that closed it. Apps see no change. (#11332)
- Internal: Markdown records its streaming fade-in refs as an exception to the runtime's ref rule, with tests that pin why it is harmless. (#10939)
- Internal: the rule that ends a container's press for a press on a nested control is named for every pointer it covers, and its comments and records say what it does. No change to any component's behavior or API. (#11304)
Contributors
Thanks to everyone who contributed to this release:
0.7.14
New Features
- ComplexSelector:
disabledMessageexplains why a disabled selector is disabled. WithisDisabled, a tooltip shows the reason on hover and keyboard focus, and the reason describes the trigger througharia-describedby. The disabled trigger keeps its tab stop, and pointer, keyboard and the imperative handle still cannot open the popup. WithrenderTrigger, the caller owns the control, anddisabledMessageworks with it too: the tooltip and the description go to that control. Drop the control's own tooltip while the selector is disabled, for exampletooltip={isDisabled ? undefined : 'Filter'}, so it never shows two. Separately, a caller's ownaria-disablednow reaches an enabled built-in trigger. (#5984) - An anchored layer's entrance now slides from, and scales about, the side the layer lands on. Before, a layer that flipped because its requested side had no room still slid from that requested side, onto its trigger. The entrance also scales about the point where the layer meets its trigger, not the center of its box. A Selector list that opens over its selected item scales about the trigger's center and does not slide. This applies to Popover, DropdownMenu and its submenus, ContextMenu, Selector, ComplexSelector, Tooltip, HoverCard, Breadcrumbs and PowerSearch menus, and any layer that uses the shared entrance. Built-in layers have no option that keeps the old entrance. The public
layerAnimationsstyles now also settransform-origin; a caller's owntransformOriginlisted after them still wins. (#10771) useMenuPresswith nolongPressDelayMsnow follows DropdownMenu's finger rules on every device: a finger or a pen opens the menu as it presses (inside a scroll view, once the 150 ms content-touch delay has passed), and the finger that opened it picks a row only after moving 10 px. To keep the previous behavior, a 500 ms hold and a pick at the opening finger's lift, passlongPressDelayMs: 500. (#8078)- Under a finger or a pen, on every device, the trigger of an anchored DropdownMenu or MoreMenu now opens its menu as it is pressed, instead of after a 500 ms hold. Inside a scroll view it opens once the 150 ms content-touch delay has passed with no scroll, so a scroll that starts on it still scrolls. To keep the previous behavior, a tap that opens at the lift and a 500 ms hold, pass
presentation="popover". A menu shown as a bottom sheet, and a mouse, are unchanged. (#8078) - SegmentedControl: a drag that drifts off the control keeps choosing by its horizontal position, clamped to the end segments, and the lift commits that segment. A mouse or a pen drags the same way. Escape or a browser cancel takes the press back, and the highlight returns at once. (#10978)
- Tokenizer is now an InputGroup-compatible control (#3520). Inside an
InputGroupit consumesInputGroupContextinstead of rendering its ownField, so the group owns the single label, description, and status chrome — no more duplicated label or nested field wrapper. The typeahead input is named by the group label plus the Tokenizer's own label (composed withgetInputARIA, soaria-describedbymerges the group's description/status with the input-local disabled reason rather than replacing it), and the control adopts the sharedgroupStyles.inGroupborder/radius treatment so it joins the group's seam. The group also owns size, the disabled state, and validation: a disabled group disables its Tokenizer, a grouped Tokenizer takes the group'ssize(an explicit largersizeno longer escapes the row), and its localdescription/statusare neither referenced fromaria-describedbynor painted beside the group's status. Because the group is a fixed-height single-line surface, a grouped Tokenizer keeps its tokens on one scrolling row instead of wrapping past the shared border — cap selections withmaxEntriesor summarize them withtokenOverflowBehavior. Its end controls (the clear button,endContent, and the busy indicator) hold the end of that row: tokens scroll beside them, never underneath. The row hides its native scrollbar and fades whichever edge hides tokens instead; forced colors bring back a thin native scrollbar. Keyboard users reach hidden tokens through their remove buttons (Shift+Tab from the input), and a disabled Tokenizer's row becomes its own Tab stop while it overflows, named by the Tokenizer's label, so the arrow keys can scroll it. (#4405) - TimeInput, DateTimeInput: under a finger, the bottom sheet's minute wheel loops, as UIDatePicker's does: past 59 comes 00, and the hour stays, as on iOS. A drag, a fling, a tap or an arrow key passes the seam. Home, End and a click on a minute never pass it. The hour wheel does not loop yet. Each minute is still listed once for assistive technology. (#10953)
Fixes
- When a page mounts both the package's AppShell and a swizzled AppShell as outermost shells, only the first now keeps the fixed main-region id; the other takes a generated id, as two package shells already did. Before, each copy kept its own claim list, so both shells used
astryx-app-shell-mainand the page had a duplicate id. No API changes. (#11208) - BottomSheet: a finger's pull down on the sheet's content is handled by the sheet's touch listeners alone, and it releases at the speed of the whole pull. Before, the content's pointer handlers, which serve a mouse or a pen, began the same drag first and took pointer capture, and the capture change cancelled that drag one move later. The touch listeners then began the drag again, or, in Chromium, the content's own pan could start under it. The release speed counted only the moves after the drag began, so a fast flick on the content that the page received as two or three moves read as no speed and sprang back, where the same flick on the grab handle closed the sheet. A flick on the content now closes the sheet as a flick on the grab handle does. This also applies to the sheets that Tokenizer and PowerSearch open. A mouse or pen pull from the content also releases at the speed of the whole pull. No release threshold changes. (#11145)
- BottomSheet: a move of a touch drag no longer restyles the sheet's content. Each move writes the scrim's opacity on the dialog as a custom property, and the property inherited into the sheet, so the browser restyled every element in the sheet on every move: 51 elements a move in a Tall sheet with a short list, 84 in PowerSearch's Filters sheet with three filters, and more with more content. The sheet's panel now ends that inheritance, and a move restyles the dialog, its backdrop, the panel and the edge tint. The scrim follows the drag as before. This applies to the sheet that owns the scrim: a single BottomSheet, or the first sheet of a stack, such as PowerSearch's Filters sheet and Tokenizer's sheet. (#11154)
- BottomSheet: in Safari, and in every browser on iPhone and iPad, a swipe on the sheet's content that starts slowly now moves the sheet, so a slow swipe down can close it. Before, on content that fits, when the finger's first move was 8 px or less, in either direction, the sheet stopped answering that swipe: it stayed open, or moved a few pixels and fell back. Fast swipes and swipes on the grab bar already worked, and Chromium browsers were not affected. The fix applies wherever the touched content has nothing to scroll: a sheet whose content fits, and the fixed header or footer around a list. That includes the PowerSearch and Tokenizer sheets. At the top of a list that scrolls, a pull down now also moves the sheet when the finger first wobbles up by less than 5 px; a move up of 5 px or more still scrolls the list. In every browser, the sheet now decides who owns a touch on its content once, at the first move past 8 px. A mostly vertical pull at a scroll edge is the sheet's. A mostly sideways move, such as a swipe along a row of chips, is not the sheet's for the rest of that touch. Before, at the top of a list, a sideways swipe that drifted more than 8 px down, or a pull that began more sideways than down, also moved the sheet. (#11140)
- Button: a disabled or loading submit or reset Button, including one in a disabled ButtonGroup or InputGroup, no longer submits or resets its form when clicked in server-rendered HTML before the page hydrates or when JavaScript fails to load. It renders as a plain button until hydration, then takes its own type again, with no change to what people see or hear. (#11107)
- A Carousel's scroll buttons no longer cover the scroller's keyboard focus ring. Each button now sits just inside the ring instead of straddling the carousel's edge, so the whole ring stays visible while the scroller has focus (#10722). (#10726)
- A transient copy that carries an animation still waiting for its first frame now runs it in step with the original. On a busy page, the SideNav rail's leaving copy could start the toggle's press fade a frame or more after the toggle's own. (#10983)
CommandPalette: refresh results when itssearchSourcechanges while it is open. (#9679)- createISOTimeString answers null unless the trimmed string is H:M or H:M:S with one or two digits per field (a seconds fraction is still accepted and dropped), instead of reading "2:30 PM" as 02:30 (12 hours off) and "14:30abc" as 14:30 (#11023)
- FileInput's dropzone shows its status message below the drop area by default, so it no longer covers the drop area; an explicit
statusVariant="attached"still renders as before. (#11195) - A pan over the page that the browser doesn't take as a scroll no longer closes an open popover or selector list, and no longer taps the page element under the finger. (#11038)
- A swizzled overlay and the package's components now share one set of focus regions and one mobile keyboard model: nested focus regions from the package and a copy no longer both answer the same Tab, and package and copied fields agree on the keyboard's height, its layout guide and which elements ride it. No API changes. (#10831)
- On a phone, a press on a control at rest no longer measures the page, so a scroll that starts there does not wait. Hit areas no longer measure while the page scrolls or while a parent's animation moves them, such as a screen that slides in. A press on a control that a parent moves still measures the page. When a parent starts to move after the last measurement, the browser's own hit test decides the tap. No API changes. (#11083)
- The arrow-key hint that Toolbar, TabList and SegmentedControl show on first keyboard focus now stays until you press an arrow key or Escape, or move focus out of the group (WCAG 2.2 SC 1.4.13 Content on Hover or Focus). It used to disappear after 3 seconds, sometimes before it could be read, and Escape did not close it. Escape now closes only the hint, through the shared layer dismissal stack, and keeps focus where it is.
useKeyboardHint'sdismissAfterMsno longer defaults to 3000; leave it unset. (#10564) - Closing a Lightbox stops a video that was playing. The viewer stays mounted, so the picture and its sound would otherwise continue after Close, Escape, or a tap outside. A viewer that is already closed does not start playback either. Opening it again plays the current video when
hasAutoPlayis set. A video inside the caption stays stopped. (#10692) - A swizzled ListItem inside the package's List (or a package ListItem inside a swizzled List) now leaves the way a package row does: it keeps what it showed on screen, such as a swipe's travel, for its exit. Before, the List and the ListItem kept separate records of the rows the List reported and of the presentation a leaving row kept, so the row's exit lost that presentation. No API changes. (#11214)
- Make onClick-only TopNav items keyboard accessible (#9334) Previously, onClick-only TopNav actions could be skipped by Tab or could not be activated from the keyboard. TopNavItem now provides button semantics and Enter/Space activation while preserving its anchor ref/event types and custom link rendering. Desktop TopNavMegaMenuItem actions and drawer TopNavMenu actions now use non-submitting native buttons.This restores keyboard operation and action semantics for WCAG 2.2 A criteria 2.1.1 and 4.1.2. Disabled TopNavItem actions remain focusable but cannot activate; href navigation and the existing desktop menu keyboard model are unchanged.
- A fence plugin made with the package's
createMarkdownFenceTransformnow renders its node in a swizzled Markdown, and the reverse. Before, the copy described the plugin to its transform under its own keys, so the package's fence transform refused to run and the fence fell back to a plain code block. No new props, exports or defaults. (#11167) - Under right-to-left, plain text in
InputGroupText, aBadgelabel and aTokenlabel keeps the character order it was written in. Text with no right-to-left letter, such as a URL scheme (https://), a domain suffix (.com), a count (+3),C++, a handle (@alice) or a tag (#design), used to show reordered (//:https,com.,3+); it now lays out left to right. Text that contains a right-to-left letter keeps the page's direction, isolated from its neighbours, soiPhone جديدstill reads right to left. A rich (non-string) label or child is isolated but keeps the page's direction: mark mixed directions on your own content. PlainInputGroupTexttext with no right-to-left letter sits in an innerspan. Left-to-right pages are unchanged. (#10114) - A swizzled component that carries its own copy of Core's layout motion, spinner rotor or gesture sync now shares the package's: a layout change in one copy starts at the frame the other copy's change started in, so their glides land together; spinners from both copies are pinned to the timeline in one batch, so rings mounted together cost one style recalculation instead of one per copy; and a gesture sync running in one copy holds the other copy's gesture callbacks too. No API changes. (#11027)
- Popover: initial focus takes the first content control in document order everywhere. This changes the focused control only where
querySelectorAlldoes not return document order, as in jsdom; browsers focus the same control as before. (#11177) - Icons registered with
registerIcons()now reach swizzledIcon,CodeBlock,TableandTimestampcopies on the same React. Themes registered by name are now shared by every Core bundle loaded on one React. Each registry is one per React, so a second React on the page never renders the first one's elements. No API changes. (#11096) - A swizzled ResizeHandle or LayoutPanel now finds the package's panel or handle beside it, and the reverse. When the region collapses, focus inside the panel moves to the handle and the panel goes inert. Before, each copy kept its own records of lent panels and handles, so the panel resized, but focus could drop to the page as it collapsed. No API changes. (#11131)
- The package root and the component barrels no longer carry
'use client'. Inside a React Server Component,import {Card, Stack, Badge, Code} from '@astryxdesign/core'now renders the components that need no client code on the server, as their own modules intend; components that need the client stay client references. A Server Component that imports from the package root now builds with Next.js webpack. Client code renders the same as before. No API changes. To pass one of these components itself as a prop to a Client Component (for examplecomponents={{inlineCode: Code}}onMarkdown), pass it from a'use client'module. (#11106) - In iOS Safari, a tap that wobbles less than 5 px on content under a scroll-edge pan keeps its click. The pan now holds the finger only once it has moved 5 px along its axis. In Lab, in iOS Safari, a tap on a pushed NavigationStack screen that drifts less than 5 px toward the back swipe now runs; one that drifts 5 px or more toward it still loses its click. (#10829)
- A component built on useScrollableArea, such as ScrollableArea or BottomSheet, no longer renders again when focus moves between two descendants of a fitting viewport just after the component's own update. (#11135)
- Toast ids are now one sequence across the package and a swizzled copy of
useToast. Before, each copy counted from 1, so a toast from a swizzled Toast and a toast from the package could share an id in the same queue, and dismissing one removed the other. No API changes. (#11092) - A windowed Table keeps windowing when a text-size, zoom or theme change makes every row taller than
rowHeight. It windows at the height the rows measure, instead of rendering every row, and warns in development. Rows of unequal height still render every row. (#11000) - Without a
LayerProvider, toasts from a swizzleduseToastand from the package now show in one fallback stack. Before, each copy mounted its own fallback container, so the page showed two toast stacks that overlapped. No API changes. (#11161) - Tokenizer: with
hasEntriesOnFocus, picking a choice from the list shown on focus keeps the input focused and the list open, with the next choice active, so you can pick several in a row. The list closes when no choice remains, atmaxEntries, or when you press elsewhere, Tab away or press Escape. A pick from typed search results still closes the list. (#11031) - Typeahead and Tokenizer keep a dismissed menu closed when a search or focus bootstrap that was still running answers afterwards. Closing the menu with Escape, an outside click, Tab, or moving focus away also clears the busy indicator and drops a search still waiting on its debounce. A late answer for the same text is kept and shown the next time the menu opens, without searching again (reopening while that search still runs waits for its answer); an answer for text the person has since changed is dropped. Previously the late answer reopened the menu after it had been dismissed. (#8778)
Documentation
- AppShell's guidance on naming its navigation landmarks now says to pass
labelto TopNav andaria-labelto SideNav. SideNav has nolabelprop; it has a translated default name, andaria-labelrenames it. (#11151) - Add hook documentation and interactive table cell truncation example block for
useTruncation, demonstrating responsive string truncation and accessibility tooltips. (#10555) - InternationalizationProvider shows its examples in reading order: load a shipped locale, mirror the layout for right-to-left text (a new code example), override one string, then the calendar examples. Each live example is titled after its code example, so the two lists match. (#11094)
LinkProviderdocs say whatcomponentreceives, including thetoprop that router components read, that a link's ownasor a nearer provider wins over it, and that a disabled Link does not use it. (#11065)
Other Changes
- Internal: Core's internal finger-scroll reader accepts a ref that names the document, so Lab's ChatVirtualizer can watch the page's own scroll when it attaches to
document.scrollingElement. Apps import nothing new. (#10883) - Internal: MobileNav keeps its dialog rendered from the open until its delayed close has run through the layer runtime's presentation hold (Layer/presentationHold.ts). No behavior change. (#8590)
- Internal:
useChatStreamScroll's page-scroller rules move to one owner module: whether a container scrolls the page, where its visible area starts, and where its scroll events fire. The hook behaves as before, and the undocumented@astryxdesign/core/internal/page-scrollerentry gives the same rules to Lab's ChatVirtualizer. Internal entries are outside the public API and its compatibility promise. (#11160) - Internal: Core's reorder controller finds a collection's rows through an internal rows reader, so a later change can reorder plain elements. List behaves as before, and apps import nothing new. (#11199)
Contributors
Thanks to everyone who contributed to this release:
0.7.13
New Features
- Tokenizer forwards BaseTypeahead's
menuandonOpenChangein its inline presentation, and its handle gainsopen()andclose(). A token whose own button callsopen()with a dialog-role menu opens the dialog, and Escape returns focus to that token: focus that a press puts on a token's control, and the menu's focus return, stay there instead of moving to the input. The sheet presentation keeps its own sheet. (#10624) - Typeahead: Backspace or Delete on the selected Token clears the value, as the clear button does, when the clear button shows: it calls
onChange(null), announces the cleared value, and moves focus to the empty input. WithouthasClear, the keys start editing, as a click does. (#10847)
Fixes
- A swizzled component and the package's components now announce through one pair of live regions: messages from both join the same frame, and a copy no longer mounts a second pair that screen readers would read twice or skip. The modal announcement route is shared the same way. No API changes. (#10996)
- BottomSheet: a finger's pull on the sheet's content at a scroll edge cancels the content's native pan as soon as the pull reaches a tap's wobble (5 px), before the sheet's own drag begins at 8 px. In iOS Safari the first
touchmovea page keeps committed the touch to the content's scroll, so a slow-starting swipe down rubber-banded the content under the finger while the sheet moved beside it. A tap that wobbles less than 5 px keeps its click, while a tap that wobbles 5 to 8 px toward the edge now loses it. A real scroll is never cancelled. A mostly sideways swipe on a horizontal row is not cancelled before the sheet's drag begins; a first move past 8 px starts the drag in any direction, as before. (#10033) - A swizzled overlay that carries its own copy of the layer runtime now shares the package's: one layer stack, one modal outlet order, one gesture counter, and one record of outside dismissals, popover show and hide operations, layer surfaces and press claims per page. Before, such a copy kept its own, so Escape over a swizzled HoverCard inside a package Dialog could close the Dialog too, and the two copies could race each other's popover operations or miss each other's outside presses. No API changes. (#10998)
- A disabled Link stays announced as disabled, with its own role, when the caller also passes
aria-disabledorrole. Before, those caller props replaced Link's own, soaria-disabled={false}announced a disabled link as enabled, androle="button"announced a button that does nothing. (#11030) - Markdown's public parser drops every data: link and image URL, and
<Markdown>renders data: links and images as source text. (#11020) - Carousel snap paging: in Safari, a held row's stops and span stay on each item's start edge when the settle moves between an item's rect read and its translate read. (#10992)
Documentation
- Add hook documentation and interactive sparkline example block for
useDirection, detailing render-time direction handling and CSS logical properties best practices. (#10547) - InternationalizationProvider has a calendar example: the provider's
calendarprop shows aCalendarand aDateInputin the Japanese or Buddhist calendar, and the value stays a Gregorian ISO date. Both calendars work withoutTemporal. (#10135)
Other Changes
- Internal: Table's row virtualization now runs on one shared list-windowing module inside Core, which later long lists will reuse. The undocumented
@astryxdesign/core/internal/virtualizationentry gives Lab the same module. Table's behavior and public API do not change. Internal entries are outside the public API and its compatibility promise. (#10810)
Contributors
Thanks to everyone who contributed to this release: