What's New

Release notes and changelog for all packages.

0.7.11

New Features
  • Under a finger (a coarse primary pointer, on any touch device), Popover grows out of its trigger, wide before tall, with its edge held on the trigger, and shrinks back into the trigger when it closes. The growth plays the theme's --duration-medium-min (in the Storybook theme, the step nearest iOS's 206 ms growth) with its entrance easing, and the shrink plays its exit duration and easing, on the compositor. A close during the growth, or an open during the shrink, turns back from where the popover is. With reduced motion it cross-fades in and out, opacity only, in 200 ms or less. A fine primary pointer (a mouse) keeps its entrance. A tap that lands while it grows is ignored, and a pan started then scrolls nothing. The shrink plays on the layer runtime's exit copy, of which Popover is the first user. The growth starts in the next animation frame, before that frame paints, so the opening tap does no extra layout. (#8187)
  • DropdownMenuSubMenu accepts delay and hideDelay, in milliseconds, the same options Tooltip, HoverCard and TopNavMenu have. delay is how long a hovering pointer waits before the flyout opens (default 150), and hideDelay is how long the flyout stays after the pointer leaves (default 200). The defaults match today's timing, so nothing changes unless you pass them. Keyboard focus and touch never wait. (#10298)
  • Timestamp takes a timezoneID prop naming the IANA zone its absolute formats render in, such as 'UTC' or 'America/Los_Angeles'. An explicit zone renders identically on the server and the client, so a server-rendered absolute time no longer depends on the server's zone and hydrates without a mismatch. Omit it (or pass 'local') to keep the viewer's own zone, relative formats' visible text ignores it (configured tooltipEntries rows still follow it), and an unknown identifier warns once in development and falls back to the viewer's zone. (#9789)
Fixes
  • Animated layout glides now use the theme's --duration-medium instead of --duration-medium-min: 300 ms instead of 225 ms in the Neutral theme, and 410 ms instead of 310 ms with no theme. Their move curve, Reduce Motion behavior, and support for linear() and steps() easing stay unchanged. (#10261)
  • Under Reduce Motion, a cross-fade's move and its call's settle wait while a sampler pauses its fade, so the element never moves, and an exit's element never goes, while the paused fade still shows. (#10378)
  • Avatar initials and the default person icon paint in primary text on the neutral tint, a pair at 4.5:1 or more in light and dark mode; secondary text fell below 4.5:1 in dark mode. Initials read darker in light mode and lighter in dark mode. (#10205)
  • Banner: role="alert" now sits on the title and description only, not on the whole banner, so an urgent alert holds only its message (component:Banner FR8; WCAG 2.2 4.1.3 Status Messages). The dismiss and expand controls, their tooltips, a caller's action, and the supporting content are outside the alert. ARIA attributes passed with role="alert", such as aria-label, move with it. Other roles still land on the banner frame. Use role="alert" only for an urgent message, and announce every other message with useAnnounce. No visual change: the banner renders the same pixels as before. (#6779)
  • BottomSheet: a touch release takes the iOS sheet's measured values, and a release moving back toward where the drag began cancels. A release faster than about 1,000 px/s is a flick: it goes at least to the next detent in its direction, so a short fast flick at the lowest detent closes the sheet instead of springing back. From a higher detent, a flick that would carry past the next detent goes on, so a hard flick closes the sheet and a softer one stops at the next detent. A slow or medium touch throw now travels less than before, and a slow touch drag closes the sheet only past halfway to closed. A mouse or pen drag is unchanged. (#10234)
  • A labelled Button has its accessible name again in VoiceOver on macOS 14 (Safari 17 and WKWebView). The label sat inside a display: contents wrapper, which that WebKit drops names through, so it read an unnamed "button". The wrapper is now a flex box that takes the Button's own layout, and the Button looks the same. (#10256)
  • Under a finger, a Button or IconButton is easier to hit. Its touch target grows toward 44 px through an invisible band, as far as its neighbors leave room, and its box doesn't change. A disabled button, or a busy one that can't be interrupted, gets no band, and a button in a ButtonGroup uses the group's band. Input clear buttons now use the same band in place of their fixed 24 px overlay, and in Safari a tap on that band clears the field. Nothing changes under a mouse. Swizzling a ListItem, CheckboxInput, RadioListItem, InfoTip or SegmentedControl no longer leaves an import of the touch band's styles that can't resolve. (#10216)
  • Calendar and DateRangeInput no longer cause a hydration mismatch when the server and the browser are on different dates, for example a UTC server and a visitor already in tomorrow. Today is read only after hydration: a server-rendered Calendar shows no today marker until then, and a Calendar with no focusDate or value keeps its month grid's space empty until the browser's month is known. A DateRangeInput shows the year in its range text until then. (#10226)
  • Shift and one mouse wheel notch now scroll a Carousel row by the notch, once. Before, Firefox also scrolled the row on its own, so each notch moved it twice: React's wheel listener is passive, so Carousel could not stop the browser's scroll. A wheel with a horizontal delta, such as a trackpad swipe, and a row with nothing to scroll keep the browser's own scroll. (#10246)
  • A theme's borderRadius and padding on the chat-composer target now also set the composer's --_chat-composer-radius and --_chat-composer-padding, so the composer body, its status strip, and the concentric send and attach button radius follow the theme. With density="compact", the body keeps its compact padding, and its radius still follows. Before, the derived-variable registry filed these two mappings under chat, a key no element renders, so defineTheme({components: {'chat-composer': {base: {borderRadius: '16px', padding: '8px'}}}}) emitted only border-radius and padding on the composer root, and everything that reads the two variables kept the default geometry. (#10249)
  • CodeBlock's copy button now says when copying fails. A rejected clipboard write used to look like nothing happened. Now the button shows a cross in place of the copy icon for 2 seconds, as a copy shows its check mark (a theme that maps the code-block-copy icon slot keeps its own rest glyph during the failure), and is named, tooltipped and announced as "Failed to copy value to clipboard." (a new localized key, @astryx.codeBlock.copyFailed). A new onCopyError(error) prop receives the rejection once per failed copy; the error itself is never shown. (#10272)
  • The Core modules that read process.env.NODE_ENV for development warnings now declare it themselves, so those files type-check in a project that does not install @types/node, such as a swizzled Breadcrumbs, Stepper or TabList. Bundlers still replace the value at build time, so production builds drop the warnings as before. No API changes. (#10252)
  • A block-edge reveal or conceal, as in Collapsible, TreeList and Table's row expansion with an animatedLayout handle, now slides the revealed element's children on the same frames as the content beside it, under a still clip on the element's box. An element that paints its own box, such as Table's panelVariant="muted" panel, keeps the moving clip. On iOS Safari a moving clip ran on its own clock and parted from that content for a few frames; now the two stay together. The glide's timing and curve are unchanged. Collapsible's region now wraps its children in one inner element; selectors like region > * or :first-child on the region's children need updating. (#10296)
  • Kbd: a key badge grows with a larger text size instead of holding its fixed height, so a bigger glyph stays inside its badge. At the default text size nothing changes. The docs now list ref, say how a screen reader names the shortcut, and say that Kbd only shows keys and does not listen for them. (#10267)
  • In a List with hasDividers, a hovered or pressed row keeps both of its dividers visible through its tint, with a mouse and under a finger. The divider above the row used to merge into the tint, and under a finger both dividers did. The dividers keep --color-border; nothing hides. (#10280)
  • Overlay, AppShell and MobileNav work in a DOM with no matchMedia, such as an app's jsdom test. Before, Overlay threw on its first render, AppShell as it mounted (with React 19.2 or later), and MobileNav as it closed. Where matchMedia exists, nothing changes. (#10327)
  • Carousel paging: on a busy page, a finger held on a settling row now stops it, as on an idle page. Before, when the page received the touch and its lift together, a short hold read as a tap and the row ran on to its target. (#10330)
  • Carousel paging: a row that resizes while it settles back onto the page it left now hands back to native scrolling, instead of staying held by the paging. (#10419)
  • presentation="adaptive" no longer crashes in environments without matchMedia (jsdom tests). (#10275)
  • A Selector's list, opened over its trigger near the bottom of the screen while a software keyboard is up, now slides up and ends above the keyboard with its options in view. Before, it shrank to a sliver or opened under the keyboard. Without a keyboard it opens where it did. (#10169)
  • A searchable Selector's closed trigger now names the selected option after its label, so a screen reader announces the selection (for example "Team, Banana, button, collapsed"). (#10170)
  • BottomSheet: in iOS Safari, focus moving from a Tall sheet's field to a plain button inside a web component now rides the content down from the blur, as focus moving to any other control that brings up no keyboard does. A frame, or a custom element that can hold a field the page cannot see, still keeps the content in place. (#10388)
  • StatusDot's success, warning and error dots paint their status icon role (--color-icon-<status>) instead of the strong status fill, so the dot keeps 3:1 or more against the page and card surfaces; the warning dot used to read near 1.8:1 on a muted card. Success and error dots change colour too: they take their status icon colour, which is darker in light mode in the default theme. An icon inside a status dot now paints in the surface colour. (#10204)
  • On a touch screen with a mouse, after a finger opens a menu, a dialog, a drawer, a mobile nav or a popover, a click with a mouse that has not moved since reaches what is under it while the layer enters. Before, that click landed on the entrance's input hold and did nothing. A finger's or a pen's tap during the entrance is still ignored. A mouse that has sent no pointer event since the page loaded still meets the hold. (#10303)
  • BottomSheet: in iOS Safari, which publishes no keyboard slide, when the on-screen keyboard closes, a Tall sheet's content rides down with it on UIKit's keyboard spring, instead of jumping back to its earlier scroll once the keyboard is gone. A field that takes focus again before the keyboard is down rides back up, and focus moving to a select, whose picker takes the keyboard's place, starts no ride. In Chrome on Android, a busy page that reads the keyboard's hide late no longer moves the content back up before it settles. (#9776)
  • A toast shown over a Dialog no longer blinks out for a frame or more when the Dialog closes outside a click, for example when it closes once an awaited save finishes. The toast stays on screen while the Dialog closes. A close from a click, the Escape key or the backdrop already kept it. (#10251)
  • DateInput: under a finger, a bottom-sheet wheel's turn onto a tapped row, a key's row or a value set from outside now plays the shared settle spring from rest, instead of a fixed 300 ms ease-in-ease-out. The wheel's main interaction is a gesture, so all its motion springs; a flick's coast and a slow release's snap stay as they are. (#9924)
Performance
  • Closing a Popover, menu or other anchored layer no longer lays out the page an extra time. The layer runtime reads a closing layer's animations only when the layer's closed state declares a discrete display transition or a keyframe animation. It reads that style while the layer is still closed. Such a layer, as TopNavMegaMenu's panel is, still keeps its trigger's anchor name until its fade ends. An animation a script starts is not tracked. (#10368)
Documentation
  • FormLayout says to wrap it in a native <form>, and that <form> has no Astryx replacement. (#10349)
  • LayerProvider: editors and generated docs now show its description and example; they were attached to an internal constant. The docs no longer say that a nested provider is ignored: a nested provider keeps the outer toast configuration and mounts no second toast viewport, and one that declares inset applies its declared edges to the anchored layers in its subtree. (#10283)
  • Layout's height prop says that fill needs a container with a set height, such as AppShell's content area. (#10348)
Other Changes
  • Internal: a source comment in Carousel now says that the wheel listener reads no style or layout unless a flick holds the row. Apps see no change. (#10281)
  • Internal: the input hold's constant for the mouse's opening is named for the half side it holds, and its comment goes. Apps see no change. (#10317)
  • Internal: Core's keyboard module reads the press slop that press feedback uses for its tap route, instead of its own copy of the same 10 px, and three source comments that restated names are gone. Apps see no change. (#10389)
  • Internal: Core's keyboard module keeps a field above the on-screen keyboard where its nearest scroller can bring it up: a field in scrolling content is scrolled into view by its nearest scroller, the document included, a field in a container fixed at the viewport's bottom moves that container up by the part of it the keyboard still covers, unless the container sets its own translate, the app is moving it itself, or it is taller than the room above the keyboard, where its scroller reveals the field instead, or with none it moves only as far as the field needs, and focus moves and first taps into those fields arrive without the browser's reveal. A field in a fixed container the app positions itself (a dialog or a sheet that fills the viewport, a bar floating above the bottom edge, or a bar with its own translate) is revealed by a scroller around it there, and with none keeps the browser's own reveal. Core's fields adopt it next; apps import nothing new. (#9776)
  • Internal: the layer runtime gains one exit copy for touch presentations that animate a popover out: a static, inert copy of the closing popover, shown only in the top layer where the popover was drawn, for the close to play on. Core's other inert copies now join no form, carry no anchor name and keep their color scheme, as their documentation says. (#8186)
  • Internal: Dialog, Drawer and BottomSheet hand the toast viewport back to the page through a callback ref when they close or unmount, in place of a layout cleanup. A toast still stays on screen while the modal closes. Apps see no change. (#10351)
  • Internal: source comments in Popover's touch presentation and the transient copy now match what the code does: a touch that starts before the input hold can close the popover, and measure reads before the frame writes. Apps see no change. (#10300)
Contributors
Thanks to everyone who contributed to this release:

0.7.10

New Features
  • Carousel's hasSnap also takes useSnapPaging(), from @astryxdesign/core/SnapPaging: iOS paging on native snap's stops, under a finger and on a trackpad swipe. A flick moves one view, or one item with useSnapPaging({pages: 'item'}). A mouse wheel keeps native snapping. Only a carousel given the hook's value loads the pager, and hasSnap alone is unchanged. (#8153)
  • Lightbox: a ctrl-wheel or a trackpad pinch now zooms a photo, and a trackpad's scroll pans a zoomed photo. (#8148)
  • Lightbox's zoom now works under a finger the way the iOS Photos viewer does, on a phone, a tablet or a touchscreen laptop. Pinch the photo to zoom around your fingers, and move them to pan while you zoom. Past the zoom limits the photo gives way, then springs back when you let go, at the speed your fingers had. Double-tap zooms until the photo fills the screen, at least 2×, and keeps the tapped point under your finger; double-tap again to go back. On a phone or a tablet, a zoomed photo pans with momentum, stretches past its edges and settles back. The keyboard keeps the zoom it had, 2× about the centre, and keyboard panning now stops at the photo's edges instead of carrying it out of view. Every zoom, a double tap's and a key's included, settles on the same spring. (#8148) The photo's stage fills the viewer. A pinch on the photo no longer zooms the page, and a pinch on the controls or caption still does. With hasZoom on, a tap on the dark area beside the photo closes the viewer after the double-tap wait instead of at once; a click still closes it at once. The zoom animations run on the compositor, so they stay smooth while the page is busy. With hasZoom off, nothing changes. With hasZoom, Close, Previous, Next and the counter sit on a dark translucent backing, so they stay readable over a zoomed photo.
  • createDragToSnapPoints and its hook useDragToSnapPoints let a drag move an element along one axis and settle it on snap points (px offsets from its resting position) at the release: the nearest one, the next one in its direction after a flick faster than flickThreshold (default 1008 px/s), or the one it started from when the release moves back. The settle continues the release velocity, settleTo(index) settles without a drag, and onSettle(index) reports where it landed. createDragToSnapPoints is exported from the package root and useDragToSnapPoints from @astryxdesign/core/hooks; the CLI's templates gain a playing-card example of each. (#8658)
Fixes
  • Animated layout: the glide, the in-place swap and the edge reveal play the theme's move curve (--ease-move) over --duration-medium-min instead of a spring, so they follow the theme's character and tempo and land with the motion around them. Reduce Motion is unchanged: a cross-fade under a coarse pointer, an immediate change otherwise. The glides of AppShell's content area, Collapsible, Table's row expansion and TreeList change feel: 225 ms in the Neutral theme, 310 ms with no theme, instead of about 735 ms. A theme whose move easing is a linear() or steps() function glides on it, as the browser plays it. The segmented control's selection, which reads its timing the same way, now plays such an easing too instead of moving at once. (#10236)
  • Two AppShells on one page no longer share the main region's id. The first mounted shell keeps id="astryx-app-shell-main", so single-shell pages, skip links and selectors that name it keep working. Each other shell's main region gets its own generated id, which its skip link targets. (#10199)
  • BottomSheet: a sheet a touch drag closes leaves on its close spring, starting at the speed of the drag, and its scrim fades out with it on one clock, at the theme's tempo. A BottomSheetSwitcher flow's scrim does too. A mouse or pen drag is unchanged. (#8105)
  • A BottomSheet that opens, on its own or pushed over another sheet, modal or not, now focuses its data-autofocus field (a TextInput with hasAutoFocus) in every browser; for example, a pushed "Edit delivery note" sheet opens on its note field. A BottomSheetSwitcher step with such a field opens on it too. Before, Chromium left focus on the sheet's panel, so on Android a person had to tap the field before typing. A sheet with no such field still focuses where the browser's own dialog focusing puts it. (#10156)
  • Under a finger or a pen, holding the box of a CheckboxInput, a CheckboxList row, a RadioList option or a Switch no longer selects the text beside it, and lifting it activates the control as a tap does. On iOS such a hold selected the label's text and, except on a Switch, toggled nothing. A long press that opens a ContextMenu or runs a row's own long press no longer also toggles a box under it, and a row that opens its own menu from its contextmenu keeps its box unchanged. A long press on the label still selects its text, and a mouse is unchanged. (#10091)
  • Calendar and useCalendarNavigation keep moving the visible month when onFocusDateChange is given without focusDate. The focus date is controlled only when both props are present, as the imperative navigateTo handle already treated it; but the Previous/Next buttons and keyboard month crossing switched on the callback alone, so a listener-only calendar reported the new month and then stayed on the old one, with no way to move. The callback still fires in every mode. (#10180)
  • Inserting a token through ChatComposerInput's handle (insertToken) now reports the new value through onChange once, as typing does, and hides the placeholder. Before, a controlled host's Send button stayed disabled or sent a stale prompt. The ai-chat-landing page template drops the input-event workaround it used to sync the composer after an insert. (#10167)
  • Code: the code theme target now reflects size as data-size, so a theme can restyle code that inherits the surrounding text size (size="inherit") differently from code at the default code size. When size is omitted, no data-size attribute is rendered. (#10186)
  • CodeBlock and Carousel: the code viewport (while the code overflows) and the carousel scroller draw the theme's focus ring instead of the browser's default, and a theme's --focus-outline-* tokens reach them. Both rings sit inside their component's clipped box, so they show whole. The Carousel ring is painted by the carousel itself rather than the scroller, so the scroller's edge-fade mask no longer fades it, at rest or mid-scroll. The Carousel ring is drawn by an internal shared overlay. (#8875)
  • DateInput, TimeInput, DateTimeInput: value now accepts an explicit undefined. In a project with exactOptionalPropertyTypes, value={state} failed to compile when state held what onChange gave, because onChange sends undefined for a cleared field and an optional property no longer took one. A controlled field no longer needs a cast there. (#10129, part of #8961)
  • Dialog: when the first data-autofocus request is hidden, inert, aria-hidden or cannot take focus, the next eligible request takes initial focus. This also holds for a Dialog rendered inside an inert region of the page or in an iframe or Picture-in-Picture window (#10105, part of #4182)
  • FieldLabel's labelTooltip is now an info button after the label, named "About {label}", so keyboard and screen-reader users can reach the help (WCAG 2.2 2.1.1, 4.1.2), and a click or key press on it opens the help without focusing or toggling the field. (#6414)
  • Gestures: a pan on its own scroller takes a trackpad's scroll on the axis its touch-action keeps, as it takes a finger's; a scroller inside it still takes the wheel first. A recognizer attached with manageStyle: false leaves the element's styles to its caller for that recognizer only. (#10212)
  • Touch gestures work on a component rendered into another window's document, such as a same-origin iframe or a Document Picture-in-Picture window. The gesture host checked nodes and touches against this window's classes, so it ignored that window's own. A finger's scroll, a layer's input hold, the press delay inside a scroll view and the iOS selection lock read that window's nodes too. (#10224)
  • Animated layout: on iOS Safari, an Astryx gesture on gliding content goes to what is drawn under the finger. Gestures here are gesture recognizers, long presses, and Switch, Slider and SegmentedControl presses. Before, such a touch went to the element that sat under the finger when the glide started. A plain tap that no Astryx gesture handles still goes to that element until the glide ends, at most the theme's move duration. (#10239)
  • Lightbox: a double-click now zooms 2× about the clicked point instead of about the centre, and the next goes back; the keyboard keeps its 2× zoom about the centre. (#8148)
  • Link: inside a <Text maxLines> the link now truncates with the text. There its root lays out inline, in the text's lines, so the clamp can cut through the link, and its keyboard focus ring is inset into each line, so the clamp keeps the ring's top and bottom edges visible. Elsewhere, and for a Link that sets its own display or maxLines or renders as a button, the root keeps its inline-flex box. A Link with block-level content, such as an HStack with an icon, is not supported inside a clamped Text, because it breaks the clamp; place that composition outside the clamp. (#6021, fixed in #6038)
  • MobileNav: the drawer's content region is now a navigation landmark (<nav>) named like the drawer's dialog, so someone moving by landmarks on a phone finds the drawer's links, as they find SideNav's on a wide screen. SideNav items and a TopNav's drawer content both sit inside that one landmark. (#10130)
  • Under a coarse primary pointer (a touch screen as the main input), a button's touch press release now runs on the compositor. It keeps fading while the page's script is busy, instead of freezing at full strength and snapping off, and it paints nothing per frame. The release keeps the theme's exit motion timing. With any other pointer, a finger on a touch screen beside a mouse included, nothing changes. Under a coarse primary pointer, while a press is on or fading, Button paints it on its own ::before and sets isolation: isolate. At rest it adds neither, so a ::before you style, through xstyle or a className rule, merges into that layer only during a press. Style a child element to keep it unchanged. (#9783)
  • Under a coarse pointer, a SegmentedControl segment's touch target grows toward 44 px through an invisible hit area, stopping halfway to a neighbor. No segment changes size, and nothing changes under a mouse. (#10137)
  • SideNav: during a collapse, the copy of the expanded rail now paints at the rail's own level, just below the rail, instead of at z-index: 1 with the rail raised to 2. Page content stacks against the leaving rail as it does against the nav: a positioned sibling with no z-index no longer sits under the copy, and content positioned above the nav also covers the copy. The motion's timing and curve are unchanged, and Reduce Motion stays instant. (#10145)
  • Slider's value tooltip stays on its thumb in every frame of a drag and of the coast after a finger lifts. It trailed the thumb by up to 14 px, because it was anchored to a box that moved only when the owner rendered the new value. The tooltip now moves with the thumb by the same translate, and its anchor box keeps its place until the drag ends. (#10228)
  • DropdownMenu, ContextMenu and BreadcrumbItem menus without a header or footer: Tab or Shift+Tab on a row inside an open sub-menu flyout now closes every open level and the menu, calls onOpenChange(false) once, and lets focus move on from the trigger, as Tab already did from a top-level row (WAI-ARIA Menu Button). Before, the menu stayed open. A menu or sub-menu with a header or footer keeps its Tab cycle. (#8870)
  • useTableSelectionState, useTableTreeState, useTableColumnSettingsState and useTableColumnResize read their latest values as last committed. A render that React discards, as a suspended transition does, no longer reaches their handlers. "Select all rows" now selects the rows on screen, not those of a page still loading. A row's expand toggle, a column toggle and a keyboard resize also start from what is on screen. (#10176)
  • Timestamp: every value in the hover card now has a name for screen readers (WCAG 2.2 1.3.1). A copy button sits inside its row's value, so the card passes the description-list check, and a row without a label is named by its time zone's long name, which is visually hidden. (#9041)
  • A bottom toast now keeps its 16 px gap above the bottom safe-area inset instead of sitting on the inset's edge. Under a coarse pointer it clears at least 34 px plus that gap, even on a page that reports no inset (Safari reports one only with viewport-fit=cover). (#8047)
  • An empty toast viewport now has no box, so iOS Safari's bottom toolbar returns to the page color once the last toast leaves. Before, a toast swiped out through the bottom edge left its color on the toolbar until the page reloaded. (#8047)
  • A touch on a toast is now decided by its first move. A first move toward the toast's edge belongs to the swipe and never scrolls the page; any other first move leaves the page its scroll. The shared gesture host makes that claim, so importing Toast now brings in the host: about 24 KB gzip on its own (Toast from about 74 KB to 99 KB), and nothing more on a page whose other touch components already load it. LayerProvider without a Toast import is unchanged. (#8047)
  • A quick flick toward a toast's edge now dismisses it whatever its height. Before, a flick also had to travel 48 px (the distance that already dismisses a one-line toast), so on any toast up to 120 px tall a flick could only snap back; and its speed was timed by when the browser handled the touches rather than when they happened, which in browsers that deliver moves on the next frame made a quick flick look up to twice as slow. (#8047)
  • useImageMode samples the image once for a region written inline. The effect depended on the region object's identity, so the documented call shape (a fresh object literal each render) re-fetched and re-decoded the image on every render, and each result re-rendered, without end. The effect now depends on the region's four numbers. (#10183)
Performance
  • On a touch screen, a control that grows its touch target toward 44 px (CheckboxInput, RadioList, Switch, List rows, InfoTip, action groups) measures its neighbours in a shared pass. Each pass used to match every element on the page against the list of interactive selectors. The pass now keeps that list until an element is added, removed or moved, an attribute the list reads changes, or a control starts or stops its watch. It still reads every neighbour's box in each pass, so the touch targets are the same. Measured in Chromium at 4× CPU slowdown on a page with 240 interactive elements, a pass during a scroll took about 70% less time. (#10242)
  • While a Tooltip is open, the observer that follows its trigger through a scroll no longer reads layout to re-arm. It used to read the trigger's box once or twice and the viewport's size on each frame of a scroll. It now takes them from its own report. The Tooltip still checks its placement once per move, on the same frames as before. (#10235)
Documentation
  • ButtonGroup's docs no longer promise that arrow keys skip disabled members. Arrow keys still move between members, Home and End still jump to the ends, and the group is still one Tab stop. (#10203)
  • FieldStatus: the guidance now says that a field's status is announced when its message or type changes, not again when a repeated submit fails with the same errors, and shows how the form announces such a repeated submit, with unchanged errors, once with useAnnounce (the error count and the first error) and moves focus to the first invalid field. (#10122)
Other Changes
  • Internal: Carousel's Shift+wheel handler carries a lint suppression for the new passive-handler rule until it moves to a native listener. Apps see no change. (#10248)
  • Internal: Core's internal touch entry also names, for Lab's NavigationStack, the gesture host and the coarse-pointer check. Its scroll edge effect reads the internal finger-scroll hook and its end call. Apps import nothing new. (#8396)
  • Internal: @astryxdesign/core/internal/touch also re-exports an element's shared animator, the Reduce Motion cross-fade, and the coarse-pointer touch hit area's hook and layer, for Lab's PageControl. It is an internal entry reserved for Astryx's own packages, outside the public API. (#9669)
  • Internal: useFingerScroll(scroller, {onEnd}) calls onEnd each time a finger's scroll on the scroller ends, and the hook is re-exported from the internal touch subpath for Lab components that watch a finger's scroll. Internal entries are outside the public API and its compatibility promise; the hook is not exported from the package entry point or the gestures barrel. (#10172)
  • Internal: an internal entry reserved for Astryx's own packages exposes the Dialog's title id, inline state and syncDefaultName() (a header whose title renders after the dialog mounted asks the dialog to look for its name again), so Lab's upcoming DialogHeroHeader can name the dialog and request title focus the way DialogHeader does. A data-autofocus="dialog-title" request is tried after every explicit request, in preparation for that header; nothing a consumer sees changes (#10105, part of #4182)
  • Two source comments, LayerProvider's inset note and ToastViewport's file header, are split into shorter sentences. Nothing that runs changes. (#10244)
  • Internal: the motion foundation's resolveSettleMs gives a spring role's settling time at the theme's tempo, so a CSS part that plays with the spring can start and land with it. Not exported from the package entry point. (#8105)
  • A toast's card no longer runs a hidden transform transition, with its transitionrun and transitionend events, when a Dialog, a modal Drawer or a scrim sheet opens or closes over it. The toast already stayed in place. (#10223)
  • Internal: the UIKit constants table gains UIScrollView zooming for a photo viewer, measured on iOS 26.2. It holds the give past the zoom limits and Photos' aspect-fill double tap and maximum zoom. The zoom stage geometry that Lightbox's touch zoom is built on comes with it. Neither is exported from the package entry point, and Lightbox's touch zoom reads them. (#8147)
Contributors
Thanks to everyone who contributed to this release:

0.7.9

New Features
  • Under the touch presentation, ButtonGroup tracks a finger's or a pen's press across its buttons, like a menu. Press a button and slide across the others: the highlight follows, and the button you lift on runs. Lifting outside the group runs nothing. A mouse press is unchanged: it acts as a native button's, on the button it began on. With a finger, each button's target grows toward 44 px, up to half the gap to a neighbour, without the buttons growing. A menu trigger in the group keeps its own opening, and the keyboard is unchanged. Before, each button tracked only its own press, and sliding off it ran nothing. An enabled ButtonGroup root is position: relative under a coarse pointer, so absolutely positioned children anchor to the group. With a fine primary pointer, the group is unchanged.
  • DateInput, DateTimeInput: the bottom sheet shows the calendar. With a calendar such as 'persian', 'hebrew', or 'japanese', the bottom sheet shows months of the calendar, with its month names and the locale's digits, in panes of one fixed height, and its closed field writes the date in the calendar. Its month wheel lists the months of the selected calendar year, including leap months such as Adar I and Adar II, and a year change keeps the month or moves to its common counterpart (Adar I becomes Adar). Year labels carry the era, such as 令和8, and a year in which the era changes is labeled with the era of the shown month, as on iOS: 2019 reads 平成31 in January and 令和元 in July, and the month heading follows the same date, so January 3, 1989 reads 昭和64年1月. A provider locale with a -u-ca- keyword keeps the Gregorian sheet; set calendar to choose a calendar. Values stay Gregorian ISO dates. (#9842)
  • Core gains an internal parser for dates typed in a calendar system. It reads dates typed in any CalendarSystem, in any decimal digits, with month and era names, leap months such as Adar I, and Japanese eras such as 令和元年, and returns a Gregorian date. A date the calendar does not have is rejected and never adjusted. It also writes the committed text and the format hint, and reads them back as the same date in each calendar's own locale, in English and Swedish, and in locales whose weekday names are also month or era names. No component reads typed text with it yet, and no public API changes. Calendar output does not change.
  • useCalendarDays and useCalendarNavigation take an optional calendar (default gregory) for custom month views in other calendar systems; they never read the provider's calendar.
  • DateInput, DateTimeInput: never show the native date control in a calendar it cannot show. With a calendar other than gregory or iso8601, such as 'persian' or 'hebrew', adaptive-native (the default), the deprecated nativePicker values, and presentation="native" use the calendar popover on a mouse and the bottom sheet on a touch screen, because the native date control shows only Gregorian dates. An explicit presentation="native" also warns in development. A provider locale with a -u-ca- keyword keeps Gregorian dates and the native control; set calendar to choose a calendar. Values stay Gregorian ISO dates. Without Temporal, calendars other than gregory, iso8601, buddhist, roc, and japanese show Gregorian dates and the native control as before. (#9842)
  • DateRangeInput: show the range in the calendar. DateRangeInput takes a calendar prop, such as 'persian' or 'hebrew', defaulting to the InternationalizationProvider calendar (a provider locale with a -u-ca- keyword keeps Gregorian dates; set calendar to choose one), and writes its trigger text and shows its popover calendar in it. Values stay Gregorian ISO dates. Without Temporal, calendars other than gregory, iso8601, buddhist, roc, and japanese show Gregorian dates. (#9842)
  • InternationalizationProvider takes a calendar prop (CalendarSystem, exported from @astryxdesign/core/i18n), such as 'persian', 'hebrew', 'islamic-umalqura', or 'buddhist', and exposes the resolved calendar on InternationalizationContext as calendar. A locale never selects the calendar: fa-IR resolves to Gregorian until you set calendar="persian", and a provider locale with a -u-ca- keyword, such as th-TH-u-ca-buddhist, keeps Gregorian dates; set calendar to choose one. An unknown identifier resolves to Gregorian and warns once in development. The Gregorian-aligned calendars (gregory, iso8601, buddhist, roc, japanese) work everywhere; the others need Temporal. The context keeps the requested calendar; where Temporal is missing, a date component that resolves it shows Gregorian dates and warns once in development. Astryx date components keep showing Gregorian dates, and date values stay Gregorian ISO strings.
  • Calendar shows dates in other calendar systems. Calendar takes a calendar prop (CalendarSystem), such as 'persian', 'hebrew', 'islamic-umalqura', or 'buddhist', and otherwise shows the InternationalizationProvider calendar. A provider locale with a -u-ca- keyword, such as en-u-ca-buddhist, keeps Gregorian dates; set calendar to choose one. Values do not change: value, min, max, focusDate, and every callback stay Gregorian ISO dates. DateInput, DateTimeInput, and DateRangeInput show dates in the same calendar. In the selected calendar, the grid shows that calendar's months, including leap months such as Adar I and Adar II and the five- or six-day thirteenth month of the Ethiopic and Coptic calendars. Its heading, day names, and announcements use the calendar; Previous, Next, PageUp, and PageDown move one calendar month; and Shift+PageUp and Shift+PageDown move one calendar year to the same month. Day numbers use the locale's digits, and week numbers stay ISO 8601. The Gregorian-aligned calendars (gregory, iso8601, buddhist, roc, japanese) work everywhere. The others need Temporal; where the runtime lacks it, such as Safari or Node.js 24, load a polyfill like temporal-polyfill/full/global on the server and in the browser, or those calendars show Gregorian dates and warn once in development. A server-rendered app loads Temporal on the server too, since a server without it renders Gregorian markup.
  • Built-in date formats follow the calendar of the InternationalizationProvider. With calendar="persian", Timestamp's date, date_long, date_weekday, and date_time formats, the full date in its hover card and accessible name, and PowerSearch date values are written in that calendar, the same one Calendar shows. A provider locale with a -u-ca- keyword keeps Gregorian dates; set calendar to choose one. date_time keeps its time of day. time, the relative formats, system_*, and unix_seconds do not change, and without a provider calendar every output stays the same. formatSharedDate from @astryxdesign/core/utils and formatFilterValue from @astryxdesign/core/PowerSearch/utils take an optional trailing calendar argument that defaults to 'gregory'. Each of these dates names the month and day that Calendar shows for the same day, as does plainDateFormat with a calendar option other than 'gregory'. A calendar that needs Temporal shows Gregorian dates where the runtime lacks it, as the date components do.
  • DateInput, DateTimeInput: type dates in other calendar systems. Both take a calendar prop, such as 'persian', 'hebrew', 'japanese', or 'buddhist', and otherwise use the InternationalizationProvider calendar. A provider locale with a -u-ca- keyword keeps Gregorian dates; set calendar to choose one. value, onChange, min, and max stay Gregorian ISO dates. People type a date the way the locale writes it in that calendar, in any decimal digits, such as ۱۴۰۵/۸/۱۱, 1 Adar 5784, or 令和元年5月1日; the committed text, the popover calendar, and the date, date_long, and date_weekday formats use the calendar, and system_date stays the ISO date. Years are years of the calendar, so a Buddhist field reads 2026 as Buddhist year 2026: set min and max on Buddhist and Minguo calendar fields to catch a Gregorian year typed by mistake. A date the calendar does not have, such as 30 Esfand in a common Persian year, is named and never adjusted. An empty focused field without a placeholder shows an example date that the field accepts, and its description names the calendar when it differs from the InternationalizationProvider calendar. Calendars other than gregory, iso8601, buddhist, roc, and japanese need Temporal, native or a polyfill you load; without it the field shows Gregorian dates. (#9842) Typing changes for Gregorian fields too:
  • ClickableCard and SelectableCard no longer show their pressed look when a finger press starts on a control inside them, such as an info button, a button, or a link. A mouse press is unchanged. useClickableContainer returns onPointerDown; on a container that paints its press with usePressFeedback, spreading it drops a touch press that starts on a nested control. A mouse :active press paint is unchanged. A container that does not spread it works as before.
  • Table: the row-expansion toggle resolves its glyph through the table-row-expand component icon slot with state {expanded}. With no theme entry it draws chevronRight, as before. The toggle still turns the glyph a quarter turn while expanded and mirrors it in right-to-left layouts, whatever the slot resolves. A theme maps it with defineTheme({componentIcons: {'table-row-expand': …}}); null hides only the glyph, and the toggle keeps its name, aria-expanded, and its toggling.
  • Table: a sortable column's sort indicator resolves its glyph through the table-sort-indicator component icon slot with state {direction} ('ascending' | 'descending' | 'none'). With no theme entry it draws arrowUp, arrowDown, or arrowsUpDown, as before. A theme maps it with defineTheme({componentIcons: {'table-sort-indicator': …}}); null hides only the glyph, and the sort control keeps its label, its sorting, and the header's aria-sort.
  • Timestamp: the hover card's copy button resolves its glyph through the timestamp-copy component icon slot with state {copied}. With no theme entry it draws copy, then check while copied, as before. A theme maps it with defineTheme({componentIcons: {'timestamp-copy': …}}); null hides only the glyph, and the button keeps its name, tooltip, and copy action.
  • A theme chooses which shared icon a component's own icon role uses, by slot, with defineTheme({componentIcons}). The first slot is code-block-copy: CodeBlock's copy button passes {copied} and, with no theme entry, draws copy, then check while copied. A slot value is a shared icon name, null to hide the icon, a partial {icon, variant, size} request, or a pure function of the slot's state that returns one; a field the request leaves out keeps the component's own value. For the copy button, null hides only the glyph. theme.componentIcons reads back the static values. ComponentIconSlotMap and the slot value types are exported from @astryxdesign/core/Icon. astryx theme build carries static slot values into built themes and fails on a slot function, and astryx component lists a component's slots.
  • Under a finger (a coarse primary pointer), an interactive List row's hit target grows toward 44px where its neighbors leave room: the shared touch hit area measures each row and stops at half the gap to the nearest neighboring row or control. Rows look and lay out exactly as before, and a mouse is unchanged. Under a finger a list row's ::after is that invisible layer, so decorate a row with a child instead. An Item that stops delegating to a nested control now drops its pressable-container marker, so a clickable card around it gets a mouse click in the row's padding again. InfoTip's button takes taps through the same layer: it still grows toward 44px where its neighbors leave room, and waits for motion around it to end before it grows; it clears when it stops taking taps. A labelled CheckboxInput and a RadioListItem option keep their band's insets through the same hook, so the insets clear when the control stops taking taps.
  • Under a finger, on every device, the finger that opened a DropdownMenu or MoreMenu now picks a row only after it has moved 10 px (spec:AST-094 FR29, FR43), so a menu that appears under a resting finger never picks the row beneath it, however long the finger rests. To keep the previous behavior, where that finger's lift picked once the press had lasted 300 ms, pass presentation="popover". A mouse and the public useMenuPress hook are unchanged.
  • Holding a NumberInput stepper with a mouse or a pen repeats the step: the first repeat comes after 0.5 s, and later ones come faster. The field shows each repeated value as its draft and calls onChange once, when the hold ends by release or pointer cancel. A click still steps and commits at once.
  • createPanGesture(element, {axis?, onPan}) and usePanGesture(ref, {axis?, onPan}) report a drag on an element as values: onPan gets {state, translation, velocity} as the drag begins, changes, ends at the release, or is cancelled, and a finger, a mouse and a pen all drive it. A mouse or pen drag that starts on selectable text selects it instead; give text the drag should move user-select: none. axis limits the drag to 'x' or 'y'; a drag along the other axis is not reported. translation counts from where the drag began, so an element that follows it does not jump, and velocity at ended is the release velocity in pixels per second. The drag claims its touch at UIKit's 10 pt and leaves presses and long presses alone. destroy() removes every listener; the hook creates one pan for the element behind ref and destroys it at unmount.
  • LayoutPanel, ResizeHandle and SideNav take useResizable's output directly in their resizable prop: const resizable = useResizable({…}); <LayoutPanel resizable={resizable}>…</LayoutPanel> <ResizeHandle resizable={resizable} />. The output's props still works, and SideNav's true and config object are unchanged. Given the output, SideNav's rail follows the region: its width and collapse state come from the region, its toggle calls the region's collapse and expand, and the region's autoSaveId saves the width. When collapsible also sets a collapsed state, the region wins and SideNav warns in development. Any other element can use the hook's size; the Resizable docs show one sized with a StyleX dynamic style.
  • Under a finger, a labelled CheckboxInput and each RadioList option get an invisible hit area. It grows toward 44 px, never makes the target smaller than the control’s own box, and stops at half the gap to a closer neighbour, so neighbouring targets never overlap. Nothing changes size. Under a finger a RadioListItem row’s ::after is that hit area, so decorate a row with a child. A label-hidden checkbox inside another component’s row keeps that row’s target. With a mouse or trackpad nothing changes.
  • Motion: a theme's tempo now times the springs of touch motion as well as its CSS durations. Each spring keeps its shape and takes tempo times as long, and so does the animated-layout glide. Finger tracking and busy loops stay as measured. A theme with only a duration scale keeps its springs at tempo 1, even inside a theme with a tempo. The springs don't follow character yet. The motion doc says so.
Fixes
  • A backdrop press that closes a menu or popover open inside a Dialog (purpose="info"), a Drawer with its scrim, or CommandPalette now closes only that menu or popover. The next backdrop press closes the dialog, as a second Escape does. Fixes #9920.
  • BottomSheet: a finger's pull up past the top stretches the sheet on every pull, on iOS's rubber band, with no 48 px cap, unless the caller sizes or styles the sheet (an inline block size, any xstyle or class name), which keeps it. The sheet keeps enough of its surface below the screen that the page never shows. A pull on the content stretches it too once the content has no room left to scroll: at once for content that fits, and after a long list reaches its end. A mouse or a pen keeps its current stretch.
  • BottomSheet, Tokenizer, PowerSearch: a swipe that asks to close a sheet whose owner keeps it open — the Tokenizer and PowerSearch sheets ask before a changed draft is discarded — no longer leaves the page behind the sheet undimmed. The scrim the drag thinned returns with the sheet to its resting detent, so the page stays dimmed while the confirmation is open and after Keep editing; Discard still closes the sheet with its exit.
  • BottomSheet: a standalone sheet (not a BottomSheetSwitcher step) removed while it is open (rendered only while open, or removed with the rest of a view) returns focus where a close would send it, while that place is still on the page: to finalFocusRef, else the control that opened it, or into the sheet beneath. A whole stack of standalone sheets removed at once returns focus to the first sheet's finalFocusRef or opener. When none of these is left on the page, for example when the opener is removed with the sheet, focus stays where the browser leaves it. Focus the person had already moved out of a sheet, to the page body, stays where it is. A sheet that opens in the same update keeps focus, and removing a covered sheet under a top sheet that stays moves no focus.
  • The internal calendar date parser reads back the text it writes in more locales. It reads month names that start with a number, such as Latvian 1. adars for Adar I and 1. rabī for Rabi' I, and still reads 1. adars as day 1 of Adar when no other number can be the day. It reads a numeric pattern that uses two separators, such as the Hindi Buddhist format hint. In the Japanese and Minguo calendars, whose era changes between 1900 and 2100, a year without its era can read as the wrong date. There, a format hint that would otherwise leave out the era shows the narrow era when it keeps the locale's field order, such as Amharic 1/1/8 R. Where every era width moves the fields, a date of an earlier era adds the era, such as Colognian BROC 1. Jan. 12, which no longer reads as a date in 1923. Calendars with one era in that range, such as Buddhist, Ethiopic or Hijri, write the same text as before. No public API changes.
  • useChatNewMessages (which ChatLayout uses), useSpeechRecognition and useChatDictation read their callbacks and other latest values as last committed. A render that React discards, as a suspended transition does, no longer has its callbacks called on the next resize or recognition event. Its audio context is no longer used either. After such a render, useChatNewMessages also no longer flags new messages while the list follows the bottom.
  • A checked, enabled, editable CheckboxListItem row now reflects data-selected="selected" on its row, the element that carries its item and list-item targets, so a theme's selected rules for those targets restyle checked rows and the text on their fill.
  • On a touch screen, a CheckboxList row now answers a finger the same way wherever it lands. Under a finger, pressing a row's label painted the whole row while pressing its box painted only the box; under a coarse primary pointer the row is now the one touch press surface, so the row and its checkbox show the pressed state together whether the finger lands on the label, the description or the box. Where the primary pointer is fine (a mouse, a trackpad, or a pen on a desktop page), the box keeps its own press and hover, as before.
  • A disabled CheckboxInput no longer runs a caller's onKeyDown, onKeyUp, onPointerDown, onMouseDown or any other on* prop except onFocus and onBlur. Before, a disabled checkbox stayed focusable and clickable, so a key or pointer press on it still reached them; only onClick was withheld. Now a disabled CheckboxInput runs no caller handler other than onFocus and onBlur, as a disabled Slider, TextInput and TextArea do (spec:AST-085 FR2). An enabled CheckboxInput is unchanged. No API changes.
  • When a LayoutPanel beside a ResizeHandle collapses with focus inside it, focus moves to the handle, and the collapsed panel is inert and hidden from assistive technology until it opens, instead of keeping focus, and a Tab stop, in a panel of no width. This holds for a panel that takes a useResizable region's resizable props, whether the hook's own or a hand-built object, and for a panel at the region's size beside a handle given them. A collapse started from the handle or from outside the panel keeps focus where it is.
  • ComplexSelector with a status and the default attached placement now shows the status icon on its trigger in place of the chevron, as Selector and MultiSelector do, so an error is no longer shown by color alone on the field.
  • The transient copy a layout motion holds of old content (an in-place swap's old content, the SideNav rail's and AppShell content's old state during a collapse or expand) carries on the CSS animations and transitions running in it from where they were. It no longer starts each CSS animation again (a press highlight lit again, an entrance that had played playing again, whatever its fill) or shows a transition's end at once.
  • DateInput and DateTimeInput keep typed text that has not reported a date, without an error, while disabled or busy, and commit it on the next Enter or blur once editable. A new value still replaces it. Typed text whose date onChange already reported gives way to the field's value once the field is editable again, on the next Enter or blur if the field has focus. (#9842)
  • DateTimeInput: a press that never becomes a click no longer leaves its document click watchers behind when the field unmounts (#10155)
  • On a phone or tablet (a coarse primary pointer), a tap or a drag that lands while a Dialog or a Drawer is still entering no longer closes it, runs one of its actions, moves focus or scrolls the page: it reaches nothing until the entrance has played, and the dialog or drawer finishes entering and stays open. Around a Drawer without a scrim only a tap or a drag on the panel is held, and the page stays live. Keys and assistive technology stay live during the entrance, the content stays in the accessibility tree, a pinch still zooms the page, and a mouse or a trackpad still clicks: at once when it was the last pointer used, otherwise once it moves.
  • On a phone or a tablet, a finger's tap or drag that lands while a DropdownMenu is still opening is now ignored, as on iOS: the menu finishes opening, stays open and keeps focus, and nothing under the tap reacts. The finger that opened the menu still picks a row. Keys and assistive technology stay live. A mouse, a finger on a touchscreen laptop and presentation="popover" are unchanged.
  • DropdownMenu trigger tooltips stay closed after pointer selection and still reappear for returning keyboard focus.
  • FileInput: a busy or disabled dropzone now shows the no-drop cursor for a dragged file instead of the copy cursor, and the browser no longer delivers a drop the zone would ignore.
  • Focusing the clear or status button of a ghost or secondary Selector no longer also rings the whole trigger: each tab stop shows one focus ring.
  • Under a finger, a Switch or InfoTip measured while an ancestor is scaled keeps the touch insets of its unscaled layout. Before, that measurement kept the scaled frame's insets until the next resize.
  • InputGroup: a focused input now stays above an unfocused input beside it, so the neighbour's border no longer covers part of its focus ring.
  • A selected interactive Item or ListItem row now shows hover and mouse-press paint over its fill, and a highlighted Item row shows mouse-press paint. Before, the fill hid both. A highlighted row shows no extra hover, because its fill is already the hover tone.
  • Item: the item theme target now reflects the row's state as data-highlighted, data-selected, and data-disabled, so a theme can restyle a highlighted, selected, or disabled row. A row that composes Item reflects the states it passes to Item: for example, ListItem reflects selected and disabled, and DropdownMenuItem reflects disabled. The docs list className and style, give ref the root element type, and give xstyle its standard description.
  • Keep TabMenu arrow-key navigation from moving focus to the outer tab strip.
  • A layer's trigger (Tooltip, Popover, HoverCard, DropdownMenu, ContextMenu and every other useLayer caller) now carries its CSS anchor-name only while the layer is shown or its exit animation runs. A closed trigger is no anchor, so in WebKit's Linux ports a transform animation on an element that contains a closed trigger keeps running while the main thread is busy. A layer that fades out keeps its trigger's anchor name until the fade ends. If you write a layer's anchorId as an anchor name yourself, write it only while the layer is shown or its exit animation runs.
  • An anchored layer (a Popover, a menu, a Selector's or MultiSelector's panel, a Typeahead's list) that would run under the software keyboard, in Safari on iOS, now keeps its top and shrinks to end 10 px above the keyboard, its content scrolling, and grows back when the keyboard goes down; before, the keyboard covered its lower part and a button there could not be reached. A layer clear of the keyboard, or placed above its trigger, does not change.
  • A LayoutPanel whose width is the number 0, such as one given a collapsed useResizable region's resizable props or width={0}, now takes no space and shows none of its children. Before, its padding kept it about 32px wide and its children showed squeezed into that strip, one letter per line. This is visual only: keyboard and assistive-technology hiding for a collapsed panel is separate.
  • Link: the label now takes the link's own color, at rest and on hover, so on hover a primary, secondary, or accent Link tints its text with its underline and external-link icon. Before, only the underline and the icon took the hover tint. A theme override on the text target (for example text[data-color="accent"]) no longer reaches Link labels: restyle Link labels through the link target. A theme that styles the text target's color now also keeps any Text with color="inherit" on its parent's color.
  • A list row's touch press release keeps fading while the page runs script, once the release has started. ListItem, Item and TreeList rows used to freeze mid-fade until the main thread was free, and every frame of the fade repainted the row; the release now runs on the compositor, with the same color as before. Script that runs in the tap's own handlers, before the next frame, still holds the row pressed until it ends. Under a finger, while a row is pressed and through its release, the press paints on the row's ::before and the row is its own stacking context; at rest nothing of it applies, so a row's own ::before decoration and its children's stacking are as they were. During a press the layer is the row's ::before, and any ::before property a caller sets, from xstyle (which Item composes after the layer) or from a stylesheet, wins over the layer's: a decoration with its own size and background jumps to the row's corner, and the row shows no pressed fill until the release ends. Decoration that should stay through a press belongs on ::after or a child element. With a mouse or trackpad the row is unchanged: no layer and no new stacking context.
  • ChatMessageList, Tooltip and HoverCard: the chat log and the span that Tooltip and HoverCard wrap around text-only children draw the theme's focus ring instead of the browser's default. A theme's --focus-outline-* tokens now reach them. The chat log's ring sits inside its box, so the area that scrolls it no longer cuts it off.
  • Markdown's GFM autolink option (autolink: 'gfm') no longer slows to seconds on long text. The bare-email scan started over at every character of a long run, so its time grew with the square of the run: a 100,000-character word took over 10 seconds. It now starts from each @, and trailing ) are peeled off a link in one pass, so a long run costs about as much as a plain parse. Linked emails and URLs are unchanged.
  • While a finger or a pen is held in a DropdownMenu, MoreMenu or ContextMenu, the row under it now takes the pressed overlay, and no other row keeps it, so the highlight can be seen following it (spec:AST-094 FR27, FR43). A held mouse, the keyboard and a hover keep the hover overlay.
  • On a phone or tablet (a coarse primary pointer), a tap or a drag during MobileNav's slide-in reaches nothing; keys and assistive technology stay live, and a mouse or a trackpad still clicks: at once when it was the last pointer used, otherwise once it moves.
  • MobileNav: Tab now wraps inside the open navigation drawer. Tab from the last control moves to the first, and Shift+Tab from the first moves to the last, so keyboard users no longer move from inside the drawer to the browser's toolbar. The drawer uses the same focus-region module as Dialog, BottomSheet and Lightbox.
  • Dialog, AlertDialog, CommandPalette, BottomSheet, Lightbox: Tab now wraps inside an open modal Dialog, AlertDialog, CommandPalette, modal BottomSheet or Lightbox. Tab from the last control moves to the first, and Shift+Tab from the first moves to the last, so keyboard and screen-reader users no longer land in the browser's toolbar from inside these modals. They now use the same focus-region module that Drawer and Popover use. When modals nest, the innermost one handles Tab. Non-modal sheets and inline dialogs do not trap focus. Fixes #8841.
  • MultiSelector: in the open list, a repeated letter now moves to the next option that starts with it, so t, t, t over Tea, Toast and Tofu walks Toast, Tofu, Tea instead of staying on Tea. A single letter typed after a pause searches from the option after the highlighted one, not from the top of the list, as in Selector. Space still toggles the highlighted option, so a typed Space does not extend the prefix as it does in Selector. useMultiCombobox gets the same behavior. (#9921)
  • With a finger, a press that starts on a control inside a list row with onClick or href, a TreeList row with onClick or children, or a clickable or link Token with onRemove no longer makes the row or token look pressed, since it does not run the row's or token's action. A press on the row or token itself still looks pressed. Mouse presses are unchanged.
  • When an OverflowList (or a useOverflow host) resizes, it now shows the new visible set in the same frame. Before, the resize rendered after the frame painted, so one frame showed the old set at the new width: items spilled past the edge as the box shrank, or stayed collapsed as it grew. A resize now measures again in a microtask before paint, every list that one resize reports renders together, and a resize that changes nothing renders nothing. A resize whose new set can change the list's own height (a taller indicator appearing, a multi-row list filling a different number of rows or measuring a new row height, or, with behavior="observeParent", the indicator appearing or disappearing, which changes how the list fills its parent, or a list sized from its items, such as a flex item beside a menu that can shrink) still renders one frame later, as before, because rendering it before paint would make the browser report a ResizeObserver loop error. A resize that folds the list before paint can make Chromium report "ResizeObserver loop completed with undelivered notifications" once in that frame when another observer watches an outer element (Storybook's preview observes <body>); no notification is lost, and an error monitor should ignore this message. Tests: a resize the observer reports now applies in a microtask, still before paint. A test that calls a mocked ResizeObserver callback and asserts synchronously right after it should first await the update by wrapping the call in await act(async () => { … }).
  • BottomSheet and Dialog: the page no longer jumps after a sheet or a dialog closes in Safari and on iOS. Returning focus to the control that opened the overlay asks the browser not to scroll. WebKit focuses the nearest focusable ancestor of a tapped button, such as an app's tabindex="-1" main region, and records it as the opener; the focus return then scrolled the page to that region's top edge. The focus ring still follows the last input.
  • Pagination: the dots variant now exposes the APG radio group it already behaves as. Before, the dots were a group of buttons named "Go to page N", with aria-current="page" on the current page. Now the container is a radiogroup named by the page-indicators label, and each dot is a radio named "Page N" with aria-checked on the current page and no aria-current. Keyboard behavior is unchanged. A press on a dot now chooses its page on release, so sliding off before release takes the press back.
  • PowerSearch: in the sheet presentation, a placeholder longer than the trigger stays on one line and ends in an ellipsis. Before, it ran under the result count and, on a narrow field, past the field's border.
  • A press's release now fades on the theme's exit motion tokens, --duration-exit and --ease-exit, instead of 200 ms, scaled by the theme's tempo, on a curve of its own. This covers every release that fades: a finger, mouse, pen or key press on a phone or tablet, and a pen press on a desktop, on buttons, cards, switches, checkboxes, list and tree rows, tabs, menu items and action groups. With the default tokens the release is 175 ms and holds its colour a little longer before it goes. A theme that changes --duration-exit or --ease-exit now changes the release too; a theme's tempo still does, through --duration-exit. Under Reduce Motion a finger's release still fades for no more than 200 ms. A mouse press on a desktop is unchanged.
  • Under a finger, a pressable (a button, card, link, list row or any other surface) outside a scroll view now highlights in the frame the finger lands, as UIKit's controls do, instead of after a 150 ms delay. Inside a scroll view it still waits that delay, so a flick paints nothing, and a scroll that takes a held press cancels it with no fade. A page that scrolls counts as a scroll view, so on a page taller than the screen a press still waits; a control in a fixed bar, or on a page that fits, highlights at once. A mouse on a desktop keeps :active.
  • Under reduced motion, a pressed Button no longer shrinks, and ClickableCard, SelectableCard and Thumbnail change their hover, border and selection colors at once on every pointer, whatever the theme's duration. A finger's press highlight still fades out on release, within 200 ms.
  • LayoutContent, LayoutPanel and a scrollable div or span StackItem name their region while it scrolls. Before, a scrolling region was a nameless element that Chromium could make a Tab stop, so a screen reader announced nothing about it. It is now a group named by the caller's label, or by a translated "Content" (accessibility target: LayoutContent AR3, LayoutPanel AR3 and Stack AR2). A caller's role stays with only the caller's name, and Tab behavior stays the browser's.
  • Selector: after keyboard input, the active option draws the standard focus ring inside its edge, so people moving through the list with the keyboard can see where they are. The overlay fill alone measured about 1.09:1 against the listbox in light mode and 1.15:1 in dark, under the 3:1 a state indicator needs; with the stock theme the ring measures 5.39:1 (light) and 3.10:1 (dark). The ring takes its width, style and color from the --focus-outline-* tokens, like every other focus ring. After pointer input the active option keeps the fill alone, as a focused DropdownMenu row does. This includes a mouse that moves onto another option after keyboard input, without a click.
  • A disabled SideNavItem no longer runs a caller's onKeyDown, onKeyUp, onPointerDown, onMouseDown or any other on* prop except onFocus and onBlur. Before, a key other than Enter or Space on a disabled item still reached onKeyDown, every key reached onKeyUp, and pointer or mouse input that bypasses pointer-events: none (programmatic or assistive-technology input) reached onPointerDown and onMouseDown. This covers the plain, link, collapsed leaf and split-row forms; the flyout trigger of a collapsed parent item is not covered. Now a disabled SideNavItem runs no caller handler other than onFocus and onBlur, as a disabled Slider, TextInput and TextArea do (spec:AST-085 FR2). An enabled SideNavItem is unchanged. No API changes.
  • Spinner: a turning ring now wakes the main thread once every 100 turns instead of every turn. In a React app, Chromium recalculated style at the end of each turn, about seven times a second with one ring at a 525 ms turn. The ring looks and turns the same, and reduced motion still slows it to 3 seconds a turn.
  • A standalone Spinner used to mount role="status" already holding its name, so screen readers often said nothing when it appeared. It is now an indeterminate progress indicator (role="progressbar" with no aria-valuenow, named by its visible string label, its aria-label or a translated "Loading") that announces once through the shared polite channel when it appears after page load, reading its rendered text in order with stacked lines kept apart, or its accessible name (AST-020 FR15; AST-086 FR2, FR7, FR11–FR12; WCAG 2.2 4.1.3). BaseTypeahead, Typeahead and Tokenizer keep their search Spinner named and never live while they announce the search themselves, and app code silences a composed Spinner with aria-hidden. No app change is needed (AST-017 FR53): a Spinner given a role other than progressbar stays silent, as before. The lab EmojiPicker and Schedule now hide their loading rings and announce their own busy start once, and the Comments history dialog announces it inside the dialog (AST-086 FR6, FR8, FR14); their loading words stay readable. Every Spinner's indicator changes from status to progressbar, so a test that queries it by role changes, including the hidden rings inside Button, CheckboxInput, CheckboxList, CheckIndicator, ChatMessageList, ChatToolCalls, CommandPaletteInput, ComplexSelector, DateInput, DateRangeInput, DateTimeInput, DropdownMenu's sub-menus, FileInput, MultiSelector, Selector, Switch, TextArea, TextInput, Thumbnail and TimeInput, and lab's EmojiPicker, Comments and Schedule.
  • The stock theme's dark-mode accent (--color-accent) is now [#0171](https://github.com/meta/astryx/pull/0171)E3 instead of [#2694](https://github.com/meta/astryx/pull/2694)FE, so white text on an accent fill, such as a primary Button's label at rest, meets 4.5:1 (4.70:1, was 3.11:1). Hovered and pressed primary Buttons improve too (about 4.36:1 and 4.03:1, from under 3:1) but stay under 4.5:1. Light mode keeps [#0064](https://github.com/meta/astryx/pull/0064)E0. Everything else painted with --color-accent in dark mode also darkens: accent fills, focus rings and accent icons. MetadataList's "Show more", Table's sort rank and DateRangeInput's applied preset now use --color-text-accent, so their text stays readable on dark surfaces. The theme template that astryx theme template writes uses the same dark accent, and the generated color token docs list it. To keep the previous look, a theme can set '--color-accent': ['[#0064](https://github.com/meta/astryx/pull/0064)E0', '[#2694](https://github.com/meta/astryx/pull/2694)FE'].
  • A disabled Tab no longer runs a caller's onPointerDown, onMouseDown, onKeyDown or any other on* prop except onFocus and onBlur. Before, a press or key on a disabled tab still reached them, for both the button and the link form; only onClick was withheld. Now a disabled Tab runs no caller handler other than onFocus and onBlur, as a disabled Slider, TextInput and TextArea do (spec:AST-085 FR2). An enabled Tab is unchanged. No API changes.
  • A toast plays its entrance once. When a Dialog, a modal Drawer or a bottom sheet with a scrim opens or closes while toasts show, the viewport moves into it or back out, and a toast already on screen now stays where it is instead of sliding in again.
  • Toast: without a LayerProvider, a toast dismissed before the fallback viewport mounts no longer shows, and its onHide runs once with 'manual'.
  • Tokenizer: in the sheet presentation, endContent renders at the field's inline end and renderToken renders the field's tokens, as in the inline field, so the same props work on a phone under the 'adaptive' default. Their own controls act without opening the sheet: an end-content button runs its handler, and a custom token's remove control commits onChange at once and moves focus to the trigger. A tap on a token, the placeholder or the field's empty space still opens the sheet. Before, the sheet dropped both props with a development warning. renderItem, hasClear (the sheet has its own Clear all), hasEntriesOnFocus, menuWidth, tokenOverflowBehavior and hasAutoFocus still apply to the inline field only.
  • A disabled TopNavItem no longer runs a caller's onPointerDown, onMouseDown, onKeyDown or any other on* prop except onFocus and onBlur. Before, a key pressed while script had focused a disabled item, or an event dispatched to it, still reached them, in both the default and the drawer form; only onClick was withheld. Now a disabled TopNavItem runs no caller handler other than onFocus and onBlur, as a disabled Slider, TextInput and TextArea do (spec:AST-085 FR2). An enabled TopNavItem is unchanged. No API changes.
  • DateInput: under a finger, every row in view of the bottom-sheet picker's columns meets WCAG AA contrast; their edge fade is shallower.
  • Typeahead, Tokenizer: picking a result now calls onChangeQuery(''). The pick empties the input but never reported it, so an app that mirrored the query kept the text typed before the pick. A pick made while the query was already empty reports nothing, as nothing changed. (#8929)
  • useMediaQuery now shares one listener per query among all its callers, so a long list of components that ask the same query adds one listener, not one per component. Every caller still reads the same answer. It also listens on Safari before 14, which has only the older listener pair, where it threw before.
  • Gestures: a late or merged trackpad wheel that keeps the glide falling stays in the flick. When the next wheel grows instead, the new gesture keeps the late wheel's travel. A mouse wheel's notches keep their rules.
Performance
  • Under a finger, the touch-inset pass of a Switch or InfoTip resolves a control's style only when a transform scales it.
  • LayerProvider no longer carries the toast viewport. An app that imports LayerProvider from @astryxdesign/core/Layer and never imports Toast loads about 45 KB (46,161 bytes) less JavaScript (gzip). Toast registers its viewport when it is imported, and LayerProvider then renders it after the app. Without a Toast import, LayerProvider renders no empty viewport. A toast shown before the viewport mounts waits, then shows. On the server, LayerProvider renders no viewport; it mounts after hydration.
  • A single-line OverflowList no longer renders again after mount only to record an item height it never shows: it does not track the row count and item height that only its multi-row form (maxRows above 1) renders from. One whose items all fit now renders once on mount; one that collapses items still renders again for the new visible count. The public useOverflow hook is unchanged and still reports both on every path.
Documentation
  • A BottomSheet source comment names the pen beside the mouse for the resisted stretch past fully open. Nothing a consumer imports or renders changes.
  • astryx hook --list groups the motion hooks under one category, "Motion & gestures": useAnimatedLayout, useAnimator, useEntryAnimation, usePanGesture and usePressFeedback; the docs of createAnimator and createPanGesture carry the same category. The "Animation" group goes away. useLongPress, useMenuPress and the other interaction hooks stay under "Interaction".
  • Hook docs for useCalendarDays, so astryx hook useCalendarDays and astryx search return it, and a useCalendarDays — Month Grid example block: a compact month table built from the hook's weeks and dayNames, with the previous and next months' days dimmed and a Week starts on control (Sunday or Monday) that reorders both the header and the grid. Copy it with astryx template useCalendarDaysHookUsage <path>.
  • Hook docs for useIcon, so astryx hook useIcon and astryx search return it, and a useIcon — Status Row example block: a custom status row draws the success, warning and error icons with useIcon, and under a Theme that overrides those icons the same row draws the theme's icons. Copy it with astryx template useIconHookUsage <path>.
  • Hook docs for useLinkComponent, so astryx hook useLinkComponent and astryx search return it, and a useLinkComponent — Article Cards example block: custom Article cards render their title link with the component the hook resolves. Inside a LinkProvider wired to a client-side router the title navigates without a page load, as="a" gives a native anchor even inside the provider, and outside the provider the title falls back to the next provider up or a native anchor. Copy it with astryx template useLinkComponentHookUsage <path>.
  • Hook docs for useOverlay, so astryx hook useOverlay and astryx search return it, and a useOverlay — Product Quick View example block: a product Card spreads the hook's containerRef and containerProps and renders the returned scrim once over its image. Hovering the card, or moving keyboard focus into it, reveals a Quick view button, and the image link before it lets Tab reach the button. Copy it with astryx template useOverlayHookUsage <path>.
  • Hook docs for useTableSortableState, so astryx hook useTableSortableState and astryx search return it, and a useTableSortableState — Multi-Sort Orders example block: an orders Table with no sort code of its own, where clicking Customer and then Shift-clicking Total sorts by customer and then by total. Copy it with astryx template useTableSortableStateHookUsage <path>.
  • Internationalization gains a short Other calendars guide: choose a calendar on InternationalizationProvider or Calendar, values stay Gregorian ISO dates, and most calendars need Temporal (load temporal-polyfill/full/global where it is missing). A new astryx docs calendars namespace has the detail: the supported calendars, loading Temporal on the server and in the browser, why the lunisolar calendars (chinese, dangi) can differ by a day between runtimes, and ISO 8601 week numbers. The guide and Calendar's calendar prop docs say how to get identical server and browser markup for those calendars: installImplementation() from temporal-polyfill/full/shim on both sides, since the full/global import keeps a native Temporal.
  • InfoTip: the component page, astryx component InfoTip --showcase, and astryx component InfoTip --blocks now have worked examples — a showcase metric label, a row of metric definitions, and read-only settings with permission notes. InfoTip's docs list its anatomy (trigger button, info icon, help surface) and say it follows the toggletip pattern: the button reports aria-expanded="true" while the help is pinned, and a screen reader hears the help once when it pins.
  • InputGroup: the docs no longer say status paints the group border or that the group shares one focus ring. status shows its message below the group and reflects its type as data-status; a focused member stays above its neighbours. isOptional names the "Optional" indicator it shows.
  • InputGroupText: the docs now say when to use a text addon and what it is not: short fixed text or a decorative icon, read as plain text and not part of the input's accessible name. They document ref, give xstyle its standard description, and the code example no longer gives the group and its input the same label, which made a screen reader read the name twice.
  • Long comment sentences in some menu press sources and tests are split into shorter ones, and DropdownMenu's presentation description no longer says "as before". Nothing a consumer imports or renders changes.
  • The usePanGesture page opens with a draggable box in two forms side by side: the hook and createPanGesture, which takes any element, with the same StyleX styles and Astryx tokens. The playing card follows as the advanced example. The createPanGesture page points to that example, and the usePanGesture guidance warns against holding the drag offset in a large component's state.
Other Changes
  • Internal: the undocumented @astryxdesign/core/internal/calendar-system entry gives Lab's Schedule the calendar that Core's date components resolve, and the helpers that name its months, days, and date ranges as Calendar does. Internal entries are outside the public API and its compatibility promise. Lab's Schedule follows that calendar. Without a provider calendar, the accessible label of a timed event that spans days now writes its dates in the Gregorian calendar; before, the dates followed the locale's default calendar, such as the Persian calendar under fa-IR. A locale never selects the calendar.
  • onChange fires while typing only once the date is complete, and once for each date, so partial input such as 12/0 or 12/01/202 no longer reports wrong dates. A two-digit year, such as 12/01/90, or a date without a year commits on Enter or blur, and is read in the locale's field order. A one-digit or three-digit year, such as 1/5/2 or 12/01/202, is not a date: Enter or blur keeps it and shows it as invalid. parseDateInput still reads, on Enter or blur, text the field cannot otherwise read and a date the locale's field order does not have, such as 13/5/2026 in en-US.
  • A typed date outside min, max, or dateConstraints stays in the field with an error that names the allowed range, or says the date is not available when only a dateConstraints rule rejects it, instead of reverting on blur; the error shows even when you set status. Unreadable text, a date that does not exist, and an out-of-range date each announce their own message, once.
    Fixes #8958.
  • Internal: Core's internal touch entry also names, for Lab, the screen-edge pan recognizer, the spring solver, the motion resolver, UIKit's navigation table and four navigation springs, and the focus helpers that follow the last input. Core's English catalog gains @astryx.navigationStack.back. Apps import nothing new.
  • Internal: Core's internal motion engine factory is renamed createMotionEngine (from createMotionAnimator), with its types MotionEngine and MotionEngineOptions, at its source and in every internal caller. Core's internal touch entry also re-exports, by name, the UIKit gesture values, the right-to-left check, and the touch-presentation hook and query that Lab components read. Lab's useMotionEngine hook wraps the engine, and Lab's refresh control uses it. Apps import nothing new.
  • Internal: Core's internal touch entry re-exports what Lab's useRefreshControl reads. That is the pan recognizer, its hook and the gesture types, and the motion animator. It is also the motion math, the map of a companion curve, the UIKit scroll table of its pull, and the motion-role parsers. None is in the public entry. Apps import nothing new.
  • Internal: one input hold for every layer (Layer/inputHold). While a layer presents, a finger's or a pen's touch, press or click reaches nothing: anywhere around a modal layer, and only on the layer itself around a non-modal one, whose page stays live. A mouse passes once it moves, at once when the page last heard a mouse (keys and assistive technology still act, and a pinch still zooms the page). While it dismisses, every press and click reaches nothing, and the layer's content is inert. The gesture host asks the hold about each touch (holdsTouch), and isInputShield lets a hit test see past a hold's shield. Not exported from the package entry point; Dialog's and Drawer's entrance holds and MobileNav's drawer use it.
  • Internal: each spring role, and the navigation, paging and picker motion tables, register themselves when their module loads, so a spring role plays at the theme's tempo wherever it plays, with no register call. A page that plays no spring ships no springs registry. A module that imports single spring rows carries only those rows, unless it also reads the whole springs table or calls registerSpringsTable(). Not exported from the package entry point.
  • Internal: usePanGesture copies onPan into its ref at commit, not during render, before the hook's first release. A render React discards, as a suspended transition does, no longer hands the next drag to its onPan.
  • Internal: a pan gesture's begin threshold can be read from each press's first touch, so a mouse or a pen can begin a pan sooner than a finger. It is not exported from the package entry point, and nothing changes for existing callers.
  • Internal cleanups in SideNav and in how a resize handle finds its panel: a source comment that only restated the line after it goes, and one lookup function replaces two. No behavior change.
  • Internal: Spinner's rotor (the turning arc's keyframe, timing and timeline-origin pin) moves into one internal module that Lab's indeterminate CircularProgress also uses. Spinner does not change.
  • Internal: one shared reader times motion from the theme's duration and easing, as a computed transition resolves them. SegmentedControl's selection slide now reads its timing with it; its timing is unchanged, calc() tokens included.
  • Internal: DateInput and DateTimeInput keep their typed-entry state, rejection status, and commits in one shared hook instead of two copies. Typing, committing, and rejection messages are unchanged. Not exported from the package entry point. (#9842)
Contributors
Thanks to everyone who contributed to this release:

0.7.8

Experimental APIs
  • experimental.presentation is removed from Tokenizer, together with its experimental prop; use the stable presentation prop, which takes the same values. astryx upgrade rewrites static uses and leaves a TODO where it cannot prove the rewrite, such as on a Tokenizer that spreads props.
New Features
  • In Chrome on Android, on a touch screen, a Tall BottomSheet places the focused field just above the on-screen keyboard when Chrome reports it, then rides the rest of Gboard's slide; through the hide the sheet's scroll room stays while its content rides down, so nothing jumps while the keyboard is still on screen. Under Reduce Motion it cross-fades instead of moving. The browser-support guide says so.
  • Calendar: weekday headers show the locale's abbreviated names where all seven fit in four characters, and keep the short names otherwise. English now reads Sun Mon Tue instead of Su Mo Tu; French reads dim. lun. mar., and Spanish, Swedish, Norwegian, Romanian, Greek, Serbian, Turkish, German, and Traditional Chinese switch the same way. Portuguese (Portugal), Arabic, Hebrew, Polish, Danish, and Vietnamese, whose abbreviated names are longer, keep their short names. A locale Astryx ships no translations for shows its own names instead of English: the abbreviated names where they fit the same way (Indonesian Min Sen Sel), else the narrow ones (Swahili S M T). The popovers of DateInput, DateRangeInput, and DateTimeInput follow because they render Calendar. The touch bottom sheets of DateInput and DateTimeInput now show the same names as Calendar in every locale: Portuguese (Portugal) no longer runs whole words such as domingo together, and Polish, Danish, Vietnamese, Arabic, and Hebrew switch to their short names there.
  • CheckboxList takes isOptional, as RadioList and CheckboxInput do. It shows the optional indicator after the group label, so an optional checkbox group can say so, including as the exception in a FormLayout with defaultOptionality="required". Under defaultOptionality="optional" the indicator stays hidden, as for every field. A checkbox group takes no required state from a form default: with or without isOptional, its checkboxes carry no aria-required from it, and it adds no native required.
  • CheckboxList takes isRequired. The group label shows the required indicator by the same rules as every input field. While no box is checked, the first box that is neither disabled nor read-only carries native required, so the browser blocks submit and moves focus to it with its own message. Once any box is checked, the form submits. A disabled or read-only group requires nothing. Show your own error text through status.
  • CodeBlock adds startLineNumber so code excerpts show real file line numbers
  • A component doc can mark its component deprecated with deprecated: {replacement, description}: the name of the component to use instead and the modernization route. astryx search results and astryx build kit entries for that component carry the field as deprecated (a deprecated: line in their text output), and the docsite shows a Deprecated badge in the component's page header (beside any stability badge) and a notice at the top of its page that names and links the replacement, and labels it Deprecated on its components index tile and in site search. BottomSheetSwitcher sets it, naming BottomSheet; the component keeps working unchanged.
  • CheckboxInput can leave its rounded-square press layer off over a first-party replacement indicator that paints its own press. Indicators in this release are unchanged.
  • PowerSearch gains a touch surface through a new presentation prop, 'popover' | 'bottom-sheet' | 'adaptive', typed by the new exported PowerSearchPresentation, with 'adaptive' the default. bottom-sheet makes the whole field one trigger showing display-only filter tokens, and moves filter editing into a flow of tall modal sheets that stack: each step opens above the one that led to it, and dismissing a step reveals the one beneath, so no sheet has a Back action. A Filters sheet lists the active filters as rows that edit a filter, each with a trailing remove button, under a fixed header with Add filter and over a fixed footer with Clear all and Done; with no filter it shows one centered Add filter. The flow edits a draft of the filter list: adding, editing and removing a filter, and Clear all, change the draft, and Done applies it by calling onChange once per edit, in order, each with the list after that edit; a swipe, scrim or Escape close of a changed draft asks before discarding it, a clean one closes directly, and Done on a field that became read-only while the flow was open drops the draft. Clear all asks for confirmation, removes the editable filters, keeps read-only ones, and leaves Filters open. An Add filter sheet lists the fields grouped (searchable from eight fields), or the content search with the field typeahead's suggestions listed inline, and leaves its search unfocused until tapped; a field whose only operator takes no value adds at once. A value step stages operator → value and confirms from its footer, the editor on the sheet's surface, or in muted sections beside the operator choice. Closed vocabularies are full-width rows, numbers stage as typed, and string_list / entity_list values edit through the Tokenizer's own sheet presentation titled with the field label. adaptive uses the sheet on compact coarse-pointer screens and the popover otherwise, resolved the same way Selector resolves it. The sheet flow loads on demand, only when a field presents it. New @astryx.powersearch.sheet.* catalog keys for the sheets' strings; no new theming target. The API change is additive: the prop is new and optional, and no existing prop, type or export is removed or narrowed. The behavior changes only on compact coarse-pointer screens (phones), which is what 'adaptive' is for: there a PowerSearch with no presentation shows the trigger and the sheet flow, a filter reaches onChange when Done applies the sheet's draft, and menuWidth and tokenOverflowBehavior have no surface, with a development warning that names them. With a mouse or trackpad, on a screen that is not compact, in the server render and while hydrating, nothing changes. Pass presentation="popover" to keep the previous behavior on every device. Shipping this default in a patch is a product decision of the engineering owner, agreed with the owner of the compatibility policy.
  • createAnimator(element) and its hook useAnimator(ref) animate one element with the motion Astryx's components use; the hook takes the element's ref, so a gesture hook can share the element. animate springs x, y, scale, rotate and opacity to a target on the state-change motion, decay coasts any of them from a release velocity, set jumps, get and getVelocity read, and stop halts; animate and decay return a promise. Reduce Motion is planned for every call. createAnimator is exported from the package root and useAnimator from @astryxdesign/core/hooks; the CLI's templates gain a playing-cards example of each.
  • Table: let row-expansion and tree plugins include row identities in localized expand and collapse labels.
  • Tokenizer's presentation prop is stable, and its default is 'adaptive'. presentation takes 'popover' | 'bottom-sheet' | 'adaptive', typed by the new exported TokenizerPresentation. The API change is additive: the prop is new and optional, and no existing stable prop, type or export is removed or narrowed (TokenizerProps['ref'] keeps its input type, and the component also accepts a ref typed Ref<HTMLInputElement | HTMLButtonElement>). The behavior changes only on compact coarse-pointer screens (phones), which is what 'adaptive' is for: there a Tokenizer with no presentation shows a trigger that opens the bottom sheet, the sheet edits a draft so onChange reports once, on Save, ref receives the trigger button, and renderItem, renderToken, endContent, hasClear, hasEntriesOnFocus, menuWidth, tokenOverflowBehavior and hasAutoFocus are not rendered, with one development warning that names them. With a mouse or trackpad, on a screen that is not compact, in the server render and while hydrating, nothing changes. Pass presentation="popover" to keep the previous behavior on every device. Shipping this default in a patch is a product decision of the engineering owner, agreed with the owner of the compatibility policy.
  • useTooltip returns show() and hide(). show() opens the tooltip and keeps it open until hide(), Escape, a press outside, or focus leaving its trigger, and its text is announced once. hide() closes it. Both fire onShow and onHide. Under a controlled isOpen, they only call those callbacks. Use them to build a toggle-style trigger: your own button calls them on each press, sets aria-expanded and aria-controls={describedBy}, and keeps its own accessible name.
  • On a touch device with a trackpad or a mouse, such as a tablet with a keyboard, the picker wheels in the TimeInput, DateTimeInput and DateInput bottom sheets now take a trackpad's two-finger scroll as a finger: the rows follow the fingers, coast on at their lift, and rest on a row. One mouse-wheel notch turns a wheel one row, as an arrow key does, with no coast. Before, both moved the rows by each scroll's own distance, so a trackpad's momentum ran at the browser's rate and one notch moved several rows. A ctrl-scroll still zooms the page.
  • Under a coarse primary pointer, as on a phone or a tablet, the picker wheels in the TimeInput, DateTimeInput and DateInput bottom sheets now move like UIPickerView. Their rows keep the 28 px pitch and lie flat, fading toward the edges of the column in every browser; the scrolling column under a mouse tilts and fades its rows only where the browser supports scroll-driven animations, and shows a plain list elsewhere. The row under the band is in semibold accent text on its plate while the wheel rests and while a finger drags it; no row is marked while the wheel coasts, snaps or turns. A flick coasts at UIKit's deceleration onto the row UIKit's projection picks. A finger landing on a moving wheel stops it. A tap on a row turns it onto the band, and a value changed from outside while the sheet is open, as when a bound clamps the time, turns the wheel onto its row. Past the first or last row, a drag rubber-bands and the wheel bounces back. As on iOS, the value commits when the wheel comes to rest, and the coast keeps running while the page's main thread is busy. Arrow keys and clicks on a row still commit at once. Under reduced motion a flick still coasts, as scrolling does; a tap, a key or a slow release cross-fades onto its row. presentation="popover" keeps the previous surface; no value keeps the native-scroll column under a finger. Each row that reaches the band ticks with a short vibration where the browser supports it, as on Android; iOS Safari has no vibration. Under a fine primary pointer, as with a mouse on a desktop, the wheels keep the scrolling column.
Fixes
  • AlertDialog: under the touch presentation, an action lifted while the alert stays open now ends its release fade on the theme's tempo-scaled clock, as the stylesheet's fade does, instead of at a fixed 200 ms.
  • AlertDialog: under the touch presentation, its two actions are tracked as one group for a finger and a pen, the way iOS tracks an alert's actions. A press that lands on one action and slides to the other runs the action it lifts on, and lifting off both runs nothing. The pressed action highlights at once, and the highlight follows the finger between the actions. A second finger or the window losing focus ends the press with nothing run. A press on the title or the message is not tracked. A mouse press stays the native button's, and the keyboard and assistive technology keep each button's own activation.
  • Motion: a call made while an animation settles, with the element already still on screen, waits for the browser's first frame as a call from rest does. A busy page no longer skips the start of the new motion, a jump of up to about 14 px at a Switch's return.
  • BottomSheet: a sheet whose height moves by a fraction of a pixel as it starts closing now slides off instead of vanishing. This happens in Chromium, for example, when a sheet that fits its content is dismissed by a drag. The browser replaces the exit's transform transition when that transition's end value changes mid-flight. The exit treated the cancelled transition as its end and closed the dialog before the sheet had moved. It now waits for the replacement transition to finish.
  • BottomSheet: on iOS Safari the grabber stays drawn while the sheet moves between detents, instead of vanishing until the sheet comes to rest.
  • Calendar: day numbers and week numbers now use the locale's digits, the same as the month heading. Under InternationalizationProvider locale="fa-IR" the days read ۱ ۲ ۳…, and under "ar-EG" they read ١ ٢ ٣…; English is unchanged. The month panes of DateInput's touch calendar follow the same rule. The dates themselves do not change: each number is still the Gregorian day.
  • Calendar: Shift+Page Up and Shift+Page Down now move the focused day to the same date one year earlier or later, as in the WAI-ARIA date picker pattern, instead of one month. A February 29 lands on February 28 in a year without one. The year step follows the same rules as Page Up and Page Down: it changes nothing past min or max, and on a day that dateConstraints disables it focuses that month's first enabled day. useGridFocus now passes the key event to onPageUp and onPageDown, so a grid can read event.shiftKey; callbacks that take no argument keep working.
    Fixes #8947.
  • CheckboxInput, Switch and CheckboxList: in a FormLayout with defaultOptionality="required", an unchecked box, an off switch or an empty checkbox group no longer carries aria-required. A screen reader used to say "required", which on a checkbox means "must be ticked", while the form still submitted. Unchecked or off is an answer, so these controls take no required state from the form default. A CheckboxInput or Switch is required only through its own isRequired, which still sets aria-required and native required. The "Optional" and "Required" labels follow the same rules as on every other field. No code change is needed (WCAG 4.1.2).
  • clampTime without seconds now gives the nearest whole minute inside a bound that falls between minutes. Before, clampTime('08:00', '09:00:30') gave 09:00, a time outside the range.
  • Closing a ComplexSelector by clicking into another control now leaves focus in that control instead of pulling it back to the selector, as Selector and MultiSelector already do. Escape, a close from the content, or a click on nothing focusable still returns focus to the trigger. A caller-rendered trigger (renderTrigger) still gets focus back on every close.
  • Typing a numeric date into DateInput or DateTimeInput no longer reports month-first dates on the way in day-first locales.
  • The theme token --duration-exit, the standard dismissal duration, now exists. It defaults to var(--duration-fast), so it follows a theme's tempo through that token, and a theme can set it like any duration token. Before, a theme or component that read var(--duration-exit) found no value. The motion and token docs, and the theme template's token list, name it.
  • A text selection that an action's own handlers make when a claimed mouse or pen press lifts on it now stays. Before, the drag's selection hold put the press's selection back over it. When the handlers change nothing, the press's selection still comes back, as before.
  • Under focusTrigger="auto", a HoverCard now decides whether focus opens it when the focus arrives, as Tooltip does. A roving-tabindex trigger that was tabindex="-1" when the card attached, such as a toolbar member, opens on arrow-key focus, and a focusable trigger such as a <summary> or an SVG link opens on focus.
  • A HoverCard whose trigger is text written around an expression, such as Edited {when}, now wraps that text in its focusable trigger, so hover and keyboard focus open the card, the trigger carries its popup attributes or description, and it shows the same hover cue as a plain text trigger. Before, such text had no trigger at all.
  • When a HoverCard's trigger element is replaced after mount, by new children or by a child component that swaps its own root element, the new element now gets the card's popup attributes or description and opens the card on hover and focus. Before, it stayed unwired until the card next opened or closed or its label changed.
  • Icon: a labelled icon component that hides itself unless a prop replaces it, such as a Heroicons icon, is now exposed to assistive technology as an image with its label. Before, the component's own aria-hidden="true" stayed on the SVG and hid the label. If a parent control already names the icon, remove label so the name is not announced twice.
  • Icon's ref now reaches the rendered <svg> for a semantic or namespaced name, as its type promises. Before, it reached the <svg> only when icon was a component; for a name, the ref stayed empty. For a name whose glyph has no <svg>, the ref is null.
  • InfoTip renders only its button and its help: the display: contents wrapper around the button is gone, and the button is the tooltip's trigger directly, built on useTooltip's show() and hide(). Hover and keyboard focus still preview the help, and a click, tap, Enter, or Space still pins it until Escape, a second press, a press outside, or focus leaving. A mouse press on a previewed help keeps it in view as it pins, and a press that ends off the button does not pin it. A right-click on a previewed help now closes it at once, as it does on any tooltip trigger. Styles that reached the button through a wrapper selector now select the button itself.
  • BottomSheet reads the on-screen keyboard from core's shared keyboard module. It now takes over focus moves into a fully expanded Tall sheet wherever a top-level document has a visual viewport and the primary pointer is coarse, Chrome and Firefox on Android included, instead of only under an iOS user agent. A pinch zoom no longer reads as a keyboard, and a pinch-zoomed page still reads the keyboard's full height. The sheet lays its keyboard room out through its own style rather than a CSS custom property. The browser-support guide documents Chrome on Android's interactive-widget viewport setting.
  • A layout motion made late in a long main-thread task, such as a tap on a slow device, now plays instead of being skipped: under Reduce Motion the side navigation rail's cross-fade showed no fade at all after such a block. A layout change's animations start on the frame time the page last read only while that frame is at most 34 ms old; otherwise they start at the moment the change makes its first animation, so the block delays the motion. A glide such a change retargets carries on from where the compositor has it. An edge that rides such a glide, as the side navigation rail's does, moves with it. In Safari, a change that reverses such an edge mid-motion reads where the glide shows on the motion's own clock, so the edge no longer trails the content. Such a reversal also starts the rail's and the content area's fades from that moment, so the rail's icons no longer flash back. A change keeps one start from its first animation through the flush of its glides, and the parts riding those glides, however long the rest of the commit runs. A change that begins after a block since the last layout motion takes a fresh start, unless it joins an earlier change in the same area whose glides have not started yet. A side navigation collapse or expand made before the rail first paints, other than by its own toggle, lands at once, so a restored state never animates on load.
  • Lightbox: a viewer that unmounts while it is open (rendered only while open, or removed with its view) now returns focus to the element that opened it, when that element is still on the page, instead of dropping it to the page. A control the user pressed to remove the viewer keeps its focus.
  • useLongPress times a hold on the touch events' own timestamps (spec:AST-094 FR16). When a busy page handles the lift late, a finger held for the full delay still reports its long press before the lift acts, instead of losing it, so a ContextMenu's long press opens on a loaded page too. A touch the page handled late no longer lengthens the hold, and a lift stamped before the deadline still cancels the press when its timer ran late. onTouchEnd and onTouchCancel take the touch event, optionally; spreading the handlers passes it.
  • Tooltip and HoverCard: a pen held on the trigger before it lifts no longer closes the tooltip or card it just opened.
  • PowerSearch: a date-only date_absolute value (isDateOnly unset or true) reads as one day in one zone — on the token, in the accessible label and announcements, and in the edit popover's date editor — and the editor writes the day picked. Before, the token showed the device's day, the label showed a date and a time in timezoneID, and the editor read and wrote the UTC day without receiving timezoneID, so west of UTC a filter opened on the day after the one its token showed and re-picking that day moved the value a day earlier. Now a date-only value (isDateOnly unset or true) is a calendar day in timezoneID, else the UTC day: the token shows that day; the accessible label and formatFilterValue show that day with no time of day (UTC midnight March 9 in Los Angeles read "Mar 8, 2024, 4:00 PM" and reads "Mar 9, 2024"); the editor opens on it; and a picked day stores as that zone's midnight — with timezoneID set this is a different instant from the UTC midnight stored before, so a caller that derived the day from the instant's UTC date reads it in timezoneID instead, and a value the old editor stored as UTC midnight under a timezoneID west of UTC now reads the day before in the editor on every device, and on the token for a viewer at or east of UTC (UTC midnight March 9 under America/Los_Angeles reads March 8 everywhere; a Los Angeles viewer's token and the label already did), the day it would have stored — re-save such values, or read them as UTC days; with timezoneID unset no stored value changes. Each absolute date_range part is read and written as a calendar day the same way in the range editor. An operator with isDateOnly: false keeps its label; its token and editor change as its own entry describes. In the sheet presentation the rows and the value step read and write the same day. The exported PowerSearchToken and a components Token override receive timezoneID (a new optional prop on PowerSearchTokenProps), and PowerSearchToken shows that day too, where it showed the label's date and time. A [fix], not a breaking change: the released popover read one value in three zones, so nothing valid relied on how a day was stored, and timezoneID is documented for date formatting. A components Editor override and PowerSearchFilterEditor receive timezoneID.
  • PowerSearch: a date_absolute operator with isDateOnly: false gets the time of day the option names. The edit popover shows a time field beside the date picker, the token shows the date and the time, and both read and write the instant in timezoneID when it is set, else the viewer's zone, so the time typed is the time shown. Before, isDateOnly was read nowhere: every date_absolute edited in the date picker and stored UTC midnight of the picked day. Only operators that set isDateOnly: false change: a value saved from their editor now carries the time entered where it carried midnight, and their token shows the time; isDateOnly unset or true is unchanged, and stored values are read as the instants they are.
  • Under a finger, a press's release now lasts until its fade has played. The touch press controller ended the release on a clock started at the lift, so when the page's script delayed the fade's first frame, the release was cut short mid-fade. It now ends when the press's release animation ends, on the surface or on a part inside it that a component draws the release on, or on its clock where no release animation runs (an instant release, a surface without one, or an engine without Web Animations). This applies to every surface the touch press controller drives: buttons, switches, checkboxes, cards, menu rows and list rows.
  • A server-rendered useResizable region whose defaultSize is a percentage and that has no containerRef hydrates with the server's markup, then resolves the percentage against the window, instead of keeping the size the server resolved.
  • A server-rendered useResizable region with an autoSaveId hydrates with the server's markup and takes its saved size in the next commit, so hydration no longer reports a mismatch and the handle announces the saved size.
  • A disabled ResizeHandle keeps its tab stop. Before, it left the tab order, so keyboard users could not reach it to hear that it is disabled. Now it stays in the tab order, as a disabled control keeps its tab stop, and it still ignores pointer and keyboard input and says so with aria-disabled.
  • ResizeHandle's grab zone stays centred on the divider whatever pillPlacement says, which now moves only the pill. An inline zone takes at most half of a pane shorter than it, and an overlay Handle takes at most half of the pane it sits in. A short item, such as a 30-minute calendar event resized from its edge, keeps its own drag, and a drag on the pill still resizes wherever the pill is drawn.
  • useScrollLock, and so Dialog, BottomSheet, Drawer, Lightbox and MobileNav, keeps the page where it is while an overlay is open. The lock used to pin <body> with position: fixed at minus the scroll offset and scroll back on release: the page's offset read 0 for the whole lock, and on iOS Safari the jump to the top brought the toolbar back, where it stayed after the overlay closed. Now the page gets overflow: hidden (on the root, or on <body> when the body's own overflow is the one the viewport uses), and where the primary pointer is coarse (phones and tablets), a one-finger pan that would scroll the page is cancelled, which iOS Safari needs because it scrolls an overflow: hidden page under a finger. Pans that a scroller inside the overlay can take, drags on a native range input, pinch-zoom, and one-finger drags on a pinch-zoomed page (they pan the zoomed view) still work. The lock no longer pins <body>, and window.scrollY keeps its value while the lock holds. The lock cancels those pans itself, leaving a touch a gesture recognizer owns to it, and judges each pan after a small slop so a swipe's first wobble does not fix the wrong axis. It follows the browser's scroll chain, so an overlay rendered inside a scrolling container still holds the page: a modal dialog's pans go to the page, not to that container. It also sets overscroll-behavior-y: none on the root and <body>, which stops the page's overscroll bounce while an overlay is open. MobileNav now takes the same lock: while it is open, the page's bounce stops and one-finger pans are held as behind any other modal, and closing it while another modal holds the page keeps that modal's scrollbar gutter.
  • A Selector's open option list is now named by the field's label in every presentation. In the popover without search, the list was named by the trigger, so a screen reader announced the selected value, or the placeholder when nothing was selected (for example "Banana" instead of "Fruit"), against WCAG 2.2 SC 4.1.2. getByLabelText(<label>) now matches the list as well as the trigger.
  • A disabled Slider no longer runs a caller's onPointerDown, onPointerMove, onPointerUp, onPointerCancel, onKeyDown, onClick or any other on* prop. Before, a press, drag or key on a disabled slider still reached them, for both the single and the range form. Now a disabled Slider runs no caller handler other than onFocus and onBlur, as a disabled TextInput and TextArea do (spec:AST-085 FR2). An enabled Slider is unchanged. No API changes.
  • Spinner keeps turning while a script runs. The ring used to move by repainting its arc on the main thread every frame, so it stopped for as long as the page ran JavaScript, which is exactly when a loading indicator is on screen. The arc now sits in its own layer that the browser turns on its compositor: through a 700 ms main-thread block it keeps turning at full rate, and it paints nothing per frame. The ring looks the same at rest and turns at the same speed; sizes, shades, the themeable vars and reduced motion are unchanged.
  • In a Table with resizable columns, the resize handle's name and width value no longer join the column header's name. Before, screen readers read "Name 60" with every cell in the column.
  • Under a finger, the time wheels in the TimeInput and DateTimeInput bottom sheets now follow iOS's date picker:
    • The AM/PM column follows the hour. Turning the hour from 11 to 12 now gives 12 PM, not 12 AM, and the AM/PM column turns onto PM. From 12 PM to 1 it stays PM.
    • A bound that falls between whole minutes, such as min="09:00:30" without a seconds column, now commits the nearest whole minute inside it, with a finger as with a mouse.
    With a mouse, each column still turns on its own.
  • Toast: a toast updated through uniqueID (collisionBehavior: 'overwrite') now updates in place, so focus on its controls stays put instead of dropping to the page. If the update removes the focused control, focus moves to a control in the toasts (such as a dismiss button) or, with none, back to where it was before entering the toasts. Dismissing a focused toast when only toasts without controls remain also returns focus there. An update that makes a toast auto-hide keeps its timer held while focus is inside it. Outside a modal, toasts in a ToastViewport no longer carry their own live region, so each toast and each update is announced once, by the viewport; while a modal hosts the viewport, each toast announces itself, because the modal hides the viewport's channel.
  • Tokenizer's bottom-sheet presentation (presentation="bottom-sheet", and the default adaptive on compact touch screens): a confirmed Clear all keeps focus on the Clear all action, now disabled with its reason, instead of moving it to the search field, which raised the on-screen keyboard over the rows the person had just cleared. The inline presentation is unchanged.
  • Typeahead, Tokenizer, PowerSearch: a search no longer stays busy forever when React renders a new search source and then discards that render, for example a transition that suspends and that a newer update replaces before it commits. The search of the source that stays now finishes: its results show, and the loading indicator and aria-busy clear.
  • In the DateInput, TimeInput and DateTimeInput bottom sheets, a wheel's Arrow, Page, Home and End keys move through its enabled values in time order, skipping disabled ones, and stop at the first or last enabled value, with a mouse as with a finger. On a 12-hour hour wheel 12 PM comes before 1 PM, so ArrowDown from 12 PM moves to 1 PM, and a key past the last allowed hour commits nothing.
  • DateInput: with a mouse, the rows of the bottom-sheet picker's columns meet WCAG AA contrast at every scroll position; enabled rows fade by the theme's text colors instead of opacity.
Performance
  • BottomSheet: opening a sheet no longer forces a layout to measure its height while it mounts; the sheet reads its height from the browser's own layout instead. On a phone-sized page with a 4× slowed CPU, a Selector's sheet shows its first frame about one frame sooner (about 110 ms to 94 ms after the tap) and the open does about 7 ms less forced layout. The open motion and the sheet's size are unchanged.
  • Popover, DropdownMenu, Carousel, ContextMenu, DateRangeInput, Markdown, MoreMenu and Table no longer load BottomSheet's container padding styles up front. Popover loads a BottomSheet on demand for its phone presentation, and a bundler that splits code put the padding module both of them use into one chunk that loads with the component, keeping every export either side uses. paddingStyles and overlayPaddingReset now have their own modules, still exported from @astryxdesign/core/Layout/padding.stylex, and isFocusDetached has its own module, still exported from @astryxdesign/core/utils. A component that uses BottomSheet's padding itself still loads it. Rendering is unchanged.
Documentation
  • Source comments above 88 kept Effects in Core now name the external system each one syncs. Nothing a consumer imports or renders changes.
  • Hook docs for useLightbox, so astryx hook useLightbox and astryx search return it, and a useLightbox — Gallery Grid example block: a grid of photo thumbnails that opens a fullscreen gallery at the clicked item.
  • Icon: list the ten palette color values and namespaced icon keys, and document className, style, and ref in every doc language.
  • IconButton: document isInterruptible, width, the form props (type, name, value, form), and the link props (href, as, target, rel), and say that a disabled IconButton with a tooltip stays focusable through aria-disabled.
  • Icon's documented color type now lists every value the component takes: the ten semantic colors and the ten palette colors (blue, red, green, gray, cyan, teal, yellow, orange, pink, purple). Before, the type listed only the semantic colors, though the description named the palette. Native platforms still draw only the semantic colors.
  • The source comment above the Effect that copies an Overlay's first-child corner radius onto its wrapper now says why it stays an Effect. New tests pin when the radius is read. Nothing a consumer imports or renders changes.
  • TypeaheadItem: the docs say that the group prop has no effect, and that results are grouped through item.auxiliaryData.group on search-source items.
Other Changes
  • Internal: the undocumented @astryxdesign/core/internal/touch-sheet entry is removed. It re-exported the touch sheets' confirmation, search-drag dismissal and draft rules for the Lab prototypes of the Tokenizer and PowerSearch sheet presentations, which no longer exist; Core's sheets import the same modules by relative path. Internal entries are outside the public API and its compatibility promise.
  • The configuration-object useResizable builds on one internal resize region, through the same size model as before, so the region's state has one implementation.
  • The internal resize factory can drive a plain handle element: it gives the element the separator's role, name, value and tab stop, and answers its pointer drag, keys, Enter and double-click. ResizeHandle and the factory derive the separator's attributes from one helper, with no behavior change.
  • Internal: useLongPress runs its long-press detection through an internal detector with no React, so a press model that runs without React can share it. The hook and its handlers behave as before; onLongPress now also comes from the committed render. Not exported from the package entry point.
  • Internal: one progress module for the motion foundation. progressCurve gives a spring's progress from 0 to 1 as a closed-form curve, mapProgress maps any curve from another (a companion's dim following a sheet, a clamped range), mapRange is the clamped linear map they share, and presentedProgressVelocity reads the velocity an interrupted motion continues from. One velocity unit throughout: progress per second. Nothing public changes; no component imports it yet.
  • Internal: the touch press controller leaves the press of an action that its group's own tracker paints (data-astryx-press-group-item) to that tracker, so one writer paints each press. A key's press on the action still paints as before.
  • Internal: press tracking imports only the UIKit timing table's press clocks, so Switch, Slider, SegmentedControl and DateTimeInput, the controls built on press tracking, no longer ship the whole table. Nothing changes in how a press behaves.
  • Internal: the scroll lock's touch guard asks the gesture system's native-scroll test whether an element under a finger can scroll, instead of keeping its own copy. The copy left out overflow: overlay, which current Chromium and WebKit compute as auto, so pages there behave the same.
  • Internal: SelectableCard reads an internal input context that Lab's SelectableCardGroup uses to render its cards as a native radio group. SelectableCard's public props and behavior do not change.
  • Internal: a horizontal Stepper stops measuring its list from the cleanup that the list's ref callback returns, not from an Effect. It still measures before the first paint, and it still stops when the list detaches or the Stepper turns vertical. Nothing a consumer imports or renders changes.
  • Internal: a theme's reduced-motion mark and its readers are in place for reducedMotion: 'always'. No theme can set it yet, so nothing changes for anyone.
  • Internal: the Tokenizer bottom sheet checks its result rows for action while it renders, not in an Effect after the commit. The development warning, its text and the rows are unchanged. Not exported from the package entry point.
  • Internal: the rules UIDatePicker adds to its wheels, measured on iOS 26.2, join the UIKit constants table: the month/year wheels changing the date, the AM/PM column following the hour, the turn back onto a bound, and the day clamped to the month. Each rule comes with its source. None is exported from the package entry point.
  • Internal: browser proofs for the touch picker wheel in Chromium and WebKit, which a finger gets on every engine. A flick coasts on UIKit's curve onto the row it projects and commits on arrival. A finger landing on a coasting wheel stops it, and it then eases onto the nearest row. A storyboard films a flick and its coast. In Chromium, the coast also keeps advancing every frame while the main thread is blocked, and does no Layout or Paint per frame. Under reduced motion, a flick still coasts as momentum with its rows flat, and a tap cross-fades onto its row, animating opacity alone for 200 ms or less. Opening the month and year wheels writes no element per year, and each year is drawn once. Under a mouse, a drag still scrolls the column onto a row.
  • Internal: the Wheel's two presentations, the scrolling column under a mouse and the picker wheel under a finger, share one listbox hook for their ids, ARIA attributes, Arrow, Page, Home and End keys, and row clicks. Each keeps where its moves start: the scrolling column steps from the row under its band, and the picker wheel from the row it is heading to.
  • Internal: the picker wheel turns from script, for the time columns that use it. Under a finger, spinTo on the wheel's ref turns it onto a row on the tap spin, then commits it as a rest would; under a fine pointer it commits the row at once. Either way it reports whether that row was committed: it refuses a disabled row and an index outside the rows, and a turn the wheel's unmounting cuts short reports that it did not arrive. Nothing public changes: the wheel is not exported from the package entry point.
  • Internal: UIPickerView's values measured on iOS 26.2 join the touch motion tables as internal constants: the row pitch, the picker's height and its rubber band, the coast's stop speed and velocity floor, the snap at rest, the tap spin and the selection tick. The pure math a wheel moves with comes with them. It projects the row a release rests on as UIScrollView sums its deceleration, coasts with the rate re-solved to stop on that row, snaps, bounces at an end, rubber-bands, and spins to a tapped row. It is checked against UIKit's recorded frames. Nothing public changes: none of it is exported from the package entry point, and themes do not set these values.
Contributors
Thanks to everyone who contributed to this release:

0.7.7

Experimental APIs
  • Tokenizer gains a touch surface behind experimental={{presentation: 'bottom-sheet' | 'adaptive'}}. bottom-sheet replaces the inline combobox with a trigger that shows the selected tokens and opens one tall modal sheet: a bordered search field on top, full-width checkbox rows that keep their place while the sheet is open and regroup selected-first on the next open, 50-row progressive rendering for long lists, a Create "…" row with a trailing Add action under hasCreate, and a footer pinned in every state with a confirmed Clear all and Save. The sheet edits a draft: rows, the create row and Clear all change the selection the sheet shows, and value changes once, when Save reports the draft through onChange with the last edit that still holds as its change; a swipe, scrim or Escape close of a changed draft asks before discarding, and a clean one closes directly. On a touch screen a direct drag on the results dismisses the keyboard without clearing the query. adaptive uses the sheet on compact coarse-pointer screens and the popover otherwise, resolved the same way Selector resolves it. The sheet surface loads on demand, so a Tokenizer that does not opt in does not carry it. The trigger describes its selected tokens to assistive technology, announcements made while the sheet is open reach assistive technology through a live region inside the sheet, with experimental passed the component also accepts a Ref<HTMLInputElement | HTMLButtonElement> because ref reaches the trigger in the sheet presentation (TokenizerProps keeps its released ref type and gains only the optional experimental), and in development the field warns once about props that have no surface in the sheet presentation (renderItem, renderToken, endContent, hasClear, hasEntriesOnFocus, menuWidth, tokenOverflowBehavior, hasAutoFocus). The sheet's strings come from the @astryx.tokenizer.* catalog; the sheet's parts expose no theming targets while the option is experimental. Anything inside Tokenizer's experimental prop may change or be removed in a patch release; omitting it keeps the stable behavior.
New Components
  • Promote InfoTip from Lab to Core, imported from @astryxdesign/core/InfoTip or the package root: an info-icon button whose press pins its help. Hover and keyboard focus preview the help, and a click, tap, Enter, or Space pins it open until Escape, a second press, a press outside, or focus leaving. Its default name is the translated "More information", and under a coarse pointer it takes taps out toward 44 px without taking a neighbour's. The @astryxdesign/lab InfoTip export is now a deprecated re-export of the Core component and is removed in the next release: import it from @astryxdesign/core instead.
New Features
  • AppShell keeps its header items and the end of its content inside the device's safe area on a phone page that opts into the full screen (viewport-fit=cover). A header region or the phone top bar reaches under the status bar and out to the screen's sides while its items stay clear of the status bar, the Dynamic Island and a landscape notch. In height="auto", a phone top bar below a banner sticks under the top inset instead of at the top edge, so its items stay clear when the page scrolls. The main content ends clear of the home indicator (its block-end padding is contentPadding plus the bottom inset, so a child that fills it ends above the indicator), in the page or in the main region's own scroller. A shell with no header region or phone top bar takes no top inset, so its content keeps its own top padding there. In landscape only the header is inset, not an inline SideNav or the content's sides. Without viewport-fit=cover the insets are zero and nothing moves. The AppShell docs say how a page and an installed web app opt in.
  • ChatComposerInput's Return key says Send on a touch keyboard. Enter already sends the message; the editor now sets enterkeyhint="send", so iOS shows its Send key instead of a plain Return. A new enterKeyHint prop, typed by the exported closed union EnterKeyHint, takes another label, such as enter for a composer whose onKeyDown makes Enter insert a line break on touch keyboards.
  • Dialog (and so AlertDialog and CommandPalette), Drawer and MobileNav no longer blur the page behind the modal, under every pointer: the 2px full-viewport backdrop blur is costly to repaint. The dim keeps the theme's --color-overlay, and in forced colors the modal keeps an edge so it still stands apart from the page. BottomSheet never blurred. A theme keeps the blur by setting backdropFilter: 'blur(2px)' on the component's modal backdrop: components.dialog.base['::backdrop'], components['mobile-nav'].base['::backdrop'], and for Drawer components.drawer.base[':modal::backdrop'], which leaves a non-modal drawer (hasScrim={false}) unblurred.
  • Under reduced motion, an indeterminate ProgressBar no longer slides: on every pointer its fill spans the whole track and gently pulses its opacity in place, from full down to 84% and back, two seconds each way. A theme's tempo does not change the pulse, and in the default light and dark themes every fill tone that stands out from the track at 3:1 still does at the pulse's lowest point.
  • Under a finger (a coarse primary pointer, on every touch device), a determinate ProgressBar moves to a new value the way iOS's progress view does: linearly, taking one second per full track of change at the theme's default tempo (0.8 s from 10% to 90%), and from wherever the fill is drawn when the value changes again mid-way. A theme's tempo scales that time. Above zero the fill never draws shorter than two track heights, and at zero it is not drawn. The motion runs on the compositor, so it keeps going while a script runs; under reduced motion, or with forced colors on, a new value lands at once. A mouse or trackpad keeps the theme's duration and easing.
  • Search fields ask a touch keyboard for its Search key and no autocorrection. The search inputs of Typeahead, Tokenizer (and so PowerSearch), CommandPaletteInput and the Selector and MultiSelector search row now carry enterkeyhint="search" and autocorrect="off". A phone keyboard then shows a Search key instead of Return and leaves names and identifiers as typed. The key is only a label: Enter does what it did before in each field.
  • SegmentedControl: under a finger, on a touch device (a coarse primary pointer), the control tracks the touch. Dragging the selected segment carries the selection along with the finger, and the segment under the finger is chosen when it lets go (onChange fires once, at the lift); letting go outside the control selects nothing. While the selection is dragged, the selected label's colour follows it, with a margin around each boundary so a finger resting on one never flickers; label weights change only at the lift, so nothing reflows under the finger. A tap selects through the browser's own click, and a pressed segment shows the shared pressed overlay; nothing lifts or dims. A vertical drag that starts on the control still scrolls the page. A commit the item's onClick vetoes sends the selection back at once; one a controlled parent adopts later lands without a bounce. With Reduce Motion the selection still follows the finger, with no chase, and only the lift cross-fades. Keyboard and assistive technology keep the click; no element is added.
  • SegmentedControl: a mouse or a pen drags the selection as a finger does. A drag from the selected segment carries it with the pointer, and the release commits the segment under the pointer (onChange fires once, at the release). A release outside the control selects nothing, and a drag that starts on another segment commits where it lifts. Under a mouse or a pen, every change slides the selection on the theme's duration and easing, not UIKit's spring, and a click slides it too. With Reduce Motion, a mouse's or a pen's drag still carries the selection, and its release lands at once. Keyboard and assistive technology keep the click.
  • SegmentedControl: under a finger the selection slides to the new segment on UIKit's spring, whether a tap, an arrow key or a new value moved it. The selection indicator is the control's own pseudo-element, so no element is added. The motion runs on the compositor and keeps moving while the main thread is busy. With Reduce Motion nothing travels or scales: the old selection fades out where it is as the new one fades in. The spring is UIKit's measured one, an internal motion role no theme retunes, and no theme value lengthens the Reduce Motion fade. With a mouse or a pen it slides on the theme's duration and easing instead.
  • Switch's press and drag work with a mouse and a pen as well as a finger: a drag past the flip point toggles the switch at the release, unless the pointer came back past where it pressed. A mouse or pen press released away from the switch leaves it alone, flipped or not, as a checkbox does. With a mouse the switch keeps its desktop look, and the value moves the thumb. On a touchscreen laptop a finger flips it by the same rule, with the desktop look.
  • Under a finger, on every touch screen, Switch moves like the iOS switch. A press lifts the thumb a little, with a soft shadow, and a horizontal drag moves it with the finger and flips the switch once the finger has travelled most of the track; lifting the finger commits. A tap toggles through the browser's own click, and a hold or a short drag toggles at the lift. The thumb stays inside the track however far the finger drags past either end, in either writing direction. A press slid off the switch and lifted outside still toggles it, as on iOS. A vertical drag scrolls the page and the switch lets go. The motion runs on the compositor, so it stays smooth while scripts run. The thumb keeps its circle and its size on every device, and under a coarse pointer the switch's invisible hit area grows toward 44 × 44 px with nothing visible added, stopping halfway to any neighbouring control so a tap goes to the nearer one. The track keeps its theme's fill, and the colour change crossfades over it. With reduced motion on, a change cross-fades instead of moving on a touch screen and is immediate with a mouse. A press shows the pressed overlay, through a drag too, and a still hold selects no text. Keyboard and assistive technology behave as before. In Chromium, a Switch retargeted right after a tap, such as one tapped again mid-travel, turns around from where it is, with no step back to the start of its travel. Switch joins Slider on the shared press tracking and touch negotiation.
Fixes
  • A Dialog with purpose="info", a Drawer's scrim, and CommandPalette now close on a backdrop press only when the press both starts and ends on the backdrop. Selecting text in a field and releasing past the edge no longer closes it and loses the input. A press on the backdrop alone still closes it, with a mouse, a pen, or a finger.
  • BottomSheet: in WebKit, including iOS Safari, a sheet at a set height whose content sits directly in it keeps its bottom padding at the end of its scroll (0 → 16 px), instead of ending flush with the last line.
  • BottomSheet: the open sheet's dialog places its panel with a flex row instead of a grid. In desktop WebKit, measured in Playwright, an update inside an open sheet lays out faster; the iOS simulator showed no difference. A percentage height (for example '50%') now takes that share of the screen at the bottom edge; before, a short sheet was cut short and a long one hung from the top of the screen.
  • BottomSheet: a sheet closed from a control inside it, such as a Done button, a Selector's search field or a menu row, marked itself inert and aria-hidden while that control still had focus. The browser then dropped focus to the page, or screen readers were left in a hidden subtree, for the length of the exit. Now a standalone sheet that closes with focus inside it stays out of inert and aria-hidden while that focus stays, and ignores pointer and keyboard activation during its exit; when the exit ends, it closes and returns focus to its opener. The exit still plays. A sheet that closes with focus elsewhere, or that focus leaves during the exit, goes inert at once, as before.
  • BottomSheet: a sheet that a Suspense boundary hid while it was closing, and then showed again, never finished closing. Its dialog stayed open, modal and inert, so the whole page under it ignored taps, clicks and focus until a reload. This happens, for example, when a sheet's action navigates to a route that suspends. Now the sheet finishes closing when it is shown again, and the page is usable.
  • A BreadcrumbItem link or button inside the AppShell mobile drawer now closes the drawer after it runs onClick, like the TopNavItem and SideNavItem rows beside it. Before, a crumb navigated and left the drawer open over the new page. A crumb marked isCurrent, which goes nowhere, leaves the drawer open. (#9465)
  • Button, IconButton: a tooltip that repeated the button's accessible name was also added as its description, so screen readers read the same words twice ("Close, button, Close"). Astryx's own close, pagination, copy and collapse buttons did this by default. Now a tooltip whose trimmed text equals the accessible name still shows, but adds no description, when Button can read that name: its aria-label, or its label when any icon or end content is a decorative Icon. A tooltip that says more, or a Button named another way (aria-labelledby, or text in its icon or end content), keeps the description.
  • A CheckboxList with an error status now makes every checkbox aria-invalid, so a screen reader announces the list as invalid as each checkbox takes focus, as Switch and the text inputs already do. The message still renders once, from the list.
  • After a gesture takes a touch, the page no longer sees that touch's late mousedown and mouseup. WebKit sends them a few milliseconds after a held tap's cancelled touchend, aimed at whatever is under the finger by then; they now go with the click.
  • Avatar, BreadcrumbItem, Button, Lightbox, SegmentedControlItem, Tab, Tokenizer: a slot whose value is 0 showed a stray "0" beside its slot, or, in SegmentedControlItem's and Tab's icons and Tab's end content, was dropped. That covers startIcon, icon, endContent, a Lightbox caption and selectedIcon. Now each slot follows the shared presence check. Empty values (null, false, '') render no slot, as an omitted one does, and 0 renders inside its slot as content. A Tab whose selectedIcon is 0 shows it while selected instead of falling back to icon. An Avatar whose status is 0 no longer shows a stray "0"; its status slot still renders only for a truthy value.
  • Pressing Enter in the typable date field of a DateInput or DateTimeInput (the pointer surface) now submits the surrounding form when nothing is typed, as in any text field. Typed text is still committed first, and that Enter does not submit. A disabled or busy field still does nothing on Enter.
  • DateRangeInput: with presets, the popover overflowed a phone-width screen. The calendar was cut off on the right, so the Saturday column and the end of a selected range were hidden, and on screens under about 364 px Next month was out of reach too. Now, when the presets and a one-month calendar do not fit side by side, the presets stack above the calendar, and the calendar and its navigation stay inside the popover. On a short screen the popover's content scrolls. Where the presets fit beside a one-month calendar, the layout does not change.
  • Dialog (and AlertDialog, CommandPalette): a dialog that unmounts while it is open, for example one rendered only while open ({isEditing && <Dialog isOpen …>}) or removed with the rest of a view, now returns focus to the control that opened it instead of dropping it to the page.
  • Opening a Drawer without its scrim from the keyboard no longer throws an InvalidStateError when its first control has a tooltip, such as a DrawerHeader close button. The tooltip now opens once the drawer is shown.
  • A toast shown while a modal Drawer is open now appears inside the drawer, above it, and can be pressed and reached with Tab, as it already does over a Dialog or a BottomSheet. Before, the toast stayed outside the drawer's modal dialog: it was inert there (a press on Undo did nothing, and Tab never reached it), and a wide drawer hid it completely. Toasts go back to the page as the drawer starts to close. A drawer without a scrim is unchanged.
  • A toast shown before a Drawer without its scrim (hasScrim={false}) opens now stays above the drawer, as it already does above a scrimless BottomSheet. Before, the drawer painted over it, so where the drawer covered the toast's corner its action could not be seen or pressed.
  • A data-mode DropdownMenu that opens as a bottom sheet from a renderTrigger now titles the sheet, and names its dialog, after the menu's aria-label, else the trigger's own name, as its popover does. It no longer reads "Menu" for every such sheet. (#9525)
  • A window blur during a pen's press, or during a press by a finger read from its pointer events, now ends it with nothing acting at the later lift, on every surface: a Switch no longer toggles at that pen's click. Where fingers come from pointer events, a second finger leaves both to the page's pinch even when the first rests on plain page. A disabled recognizer brings no blocking listener.
  • With Reduce Motion on, a layer that opens under a finger fades in over 200 ms on easeInOut, the motion foundation's Reduce Motion values, instead of the theme's fast duration and curve. Under a mouse it still appears at once.
  • A Link rendered as a button (with onClick and no href) lines up its wrapped text like the text around it, as an href Link does, instead of centring its second and later lines.
  • A disabled CheckboxList or RadioList now sets aria-disabled="true" on its group, so a screen reader announces the group itself as unavailable, not only each option, and the dimmed group label counts as the label of an inactive control.
  • A finger's tap that a DropdownMenu (or any menu on the press model) tracks now cancels that touch's touchend, on every device, so the browser sends no click and no compatibility mouse events for it. Before, a busy main thread could hold that click past the 400 ms click guard window. After a tap that drilled into a sub-menu, the late click picked the sub-menu row that had come under the finger and closed the menu. A mouse or pen release keeps the 400 ms window.
  • With Reduce Motion on (design:reduced-motion), the month arrows in the DateInput and DateTimeInput bottom-sheet calendars, Reset, and a keyboard move into another month no longer scroll the months: on a computer with a mouse or trackpad the month changes at once, and on a touch screen it changes through a short opacity dip. A second step during the dip replaces the first, and unmounting the calendar during the dip scrolls nothing.
  • Every Outline link is now in the normal Tab order, and Tab moves from link to link, as the Outline record says. Before, the outline was one Tab stop on the current heading, with arrow, Home and End keys moving between links, so a keyboard user who did not know those keys reached only one link. The arrow, Home and End keys no longer move focus between links. (#9001)
  • Popover and usePopover: in the anchored presentation, initial focus now lands within the tap or click that opens the popover, so on iOS a text or number field in it raises the on-screen keyboard at once. Focus that onShow moves inside the popover is no longer pulled back to the first control.
  • PowerSearch: Clear all keeps read-only filters. It removes only the filters the user can edit, the clear button shows only while an editable filter exists, Backspace on an empty input no longer removes a read-only filter, and Clear all announces "Editable filters removed" while a read-only filter remains. For callers, Clear all now calls onChange with the read-only filters and remove at the first removed index (0 when no filter is read-only) instead of [] at the last filter's index.
  • PowerSearch: in a read-only field (isReadOnly), Backspace on an empty input no longer removes the last filter. A read-only field now removes no filter, as its isReadOnly docs promise.
  • PowerSearch: in the popover presentation, a built-in filter token's button was named by its field and operator only ("Status: is") and gave no sign that it opens an editor. Two filters on one field sounded the same, and the visible value was missing from the name. Now the token is named by all its visible text ("Status: is Open"), has aria-haspopup="dialog" and aria-expanded, and opens an editor that is a dialog of the same name. Its remove button is "Remove Status: is Open". Token: aria-haspopup and aria-expanded now reach a clickable token's inner button, beside aria-labelledby and aria-describedby.
  • Under Reduce Motion on a touch screen, a step on a DateInput, TimeInput or DateTimeInput wheel, and a month step in the touch calendar, change under their cross-fade even on a busy page. Before, the change landed on a timer at the fade's middle, and a busy page could fire it after the fade had ended, so the rows or the month moved fully visible. Now the change lands when the fade-out ends, on the fade's own timeline, and the fade-in starts only after it, so it never shows at full opacity. The month's dip now eases each half, as the wheels' does.
  • A ResizeHandle whose resizable prop goes away in the middle of a drag now ends the drag as it does on unmount: it releases the page's resize cursor and text selection, and the region hears that its gesture is over.
  • A Selector's option list no longer fades in when Reduce Motion is on with a mouse or trackpad; it appears at once. On a touch screen it uses the shared Reduce Motion cross-fade.
  • In an open Selector, MultiSelector, CommandPalette, DateTimeInput time list or Chat trigger menu, a key that scrolls the list (End, Home, PageDown, type-to-select) keeps the highlight where the key put it, even when the mouse is resting over the list. Before, the row that scrolled under the still pointer took the highlight. A mouse that moves or presses still takes it.
  • Slider: every pointer drags a thumb by its travel, as UISlider does. A press on a thumb no longer jumps the value to the pointer: once the pointer has moved 10 px, the value follows its further travel along the track. A finger or a pen claims the drag only along the track, so a swipe across the slider scrolls the page; a mouse claims in any direction. On a touch screen each thumb takes a finger or a pen through a 48 px target, capped at half the gap to a range's other thumb, and the held thumb lifts. After a finger's flick the thumb coasts on UISlider's measured spring for about 0.6 s, onChange firing through the coast, and onChangeEnd reports the value once it settles; a slow drag, a mouse drag and a pen drag end at the release. A tap on the track sets the value when the finger lifts, and a mouse click where it lands; a right click and a macOS ctrl-click change nothing. Under reduced motion the thumb does not lift and a tap's value applies at once.
  • Toast: a toast raised while the window is in the background now starts with its auto-hide timer paused, so it can no longer disappear before the user returns to the tab.
  • A removable Token that its width cuts off now keeps its 16 by 16 remove button. The button used to shrink to 12 px wide, so its focus ring drew as an oval and its press target narrowed to 20 by 24 px. Only the label is cut now. (#9599)
  • Tooltip, HoverCard: a tap-opened tooltip or hover card whose trigger renders in another document, such as an iframe, now closes on a scroll that starts outside in that document, and on a tap outside there when the trigger takes no focus.
  • Typeahead: with focus entries on, an open list whose focus entries come back empty, or fail to load (for example after the query is cleared), now closes instead of staying open and empty. A typed search with no results still shows its message.
  • Typeahead: pressing Escape while editing the selected value now restores the value and moves focus to its token, instead of dropping focus to the page. With the list shown, the first Escape only hides the list.
  • useMediaQuery returns its server default where the window has no matchMedia, as in a test DOM, instead of throwing. Components that read it, such as Slider, now render in such a DOM; SegmentedControl, which reads it from this release, keeps rendering there.
  • A picker wheel that stops on a value outside the bounds now settles on the nearest value inside them. Before, it bounced back to the value it started from. This applies to the wheels in the TimeInput, DateTimeInput and DateInput bottom sheets. For example, with min="09:00", dragging the hour wheel from 10 to 7 settles on 9, as the iOS time picker does. A stop on a value inside the bounds is unchanged. Opening a sheet on a value outside the bounds commits nothing. When a bound changes a wheel's value while the sheet is open, as when the meridiem wheel turns past the maximum, that wheel turns onto the new value instead of jumping there. Under reduced motion, the wheel's own scrolls no longer glide. On a touch screen this travel, the step from an arrow key and a click on a row cross-fade, the rows landing while they are faded out; with a mouse or a trackpad they land at once, except the travel after a touch drag, which cross-fades on any screen.
Performance
  • Opening a Selector's list or moving its highlight re-renders only the options whose highlight or selection changes, not every option, so a long list opens sooner and arrow keys respond faster.
  • Opening a Selector with a long option list is faster: the list no longer restyles every option a second time on its first open to switch to its scrolling touch behavior.
Documentation
  • Hook docs for useOutlineFromMarkdown, so astryx hook useOutlineFromMarkdown and astryx search return it, and a useOutlineFromMarkdown — Docs Article example block: a Markdown article and an Outline built from the same string through the hook, with a button that adds a section and its linked entry.
Other Changes
  • Internal: the touch presentations' animator carries a channel on from the screen when a rebase, a set or a retarget that starts now rebuilds it after its call's first frame came late and left the start unread. The channel leaves that call with a start of its own, dated from that frame, instead of starting its curve again; the call's other channels keep waiting for the browser's start. Not exported from the package entry point.
  • Internal: the touch presentations' animator reads a call whose first frame came late, and left its start unread, as started at that frame. A retarget or a read before the browser reports the start, of now or of a later time, continues near where the screen has it instead of from the call's first value. A rebase or set that rebuilds one channel's animation in that window reads that channel's first value until the frame that commits it, and the call's other channels keep reading from the first frame. The browser's start, once read, still decides. Not exported from the package entry point.
  • Internal: ChatMessage's avatar offset variable now has the private literal name --_chat-avatar-offset instead of a hashed name, so the published stylesheet no longer declares an internal variable that looks public. The avatar's offset is unchanged. Not exported from the package entry point. (#9602)
  • Internal: a mouse or pen drag that a gesture claims takes no new text selection and keeps the page's existing one, from the claim of whichever recognizer makes it (a swipe or a recognizer waiting on another's failure included), and a drag that starts on selectable text is left to the browser, which selects that text. Not exported from the package entry point.
  • Internal: a pan follows a trackpad's two-finger scroll where its owner allows it (allowedScrollTypes: ['continuous'], UIKit's allowedScrollTypesMask; none by default), along its own axis and after the scrollers under the pointer, and never a mouse wheel's notches, which scroll what is under the pointer; the screen-edge pan takes none; and a pinch takes a ctrl-wheel from a trackpad or a mouse (AST-094 FR43, DEC-24). A watcher pan never takes the wheel, and a wheel another handler already prevented stays the page's. Input the deltas cannot place, Shift+wheel included, reads as a mouse wheel; a trackpad scroll a pan follows keeps moving at the fingers' speed until their lift is read, ends there still moving, and the momentum never moves it. Not exported from the package entry point.
  • ResizeHandle's pointer drag, keys and double-click move into one internal module, with no behavior change.
  • Internal: when a main-thread stall delivers a late trackpad wheel and bunched wheels after it, a followed pan reads the fingers' speed over the late wheel's interval, so a flick no longer coasts short. The reading never passes the speed before the stall. Not exported from the package entry point.
  • Internal: a followed trackpad pan takes no speed from a wheel within 1.5 ms of the one before, so bunched wheels after a main-thread stall no longer carry it past the fingers' travel, at 60 to 500 Hz. Not exported from the package entry point.
  • Internal: the trackpad splitter reads a bunched wheel, one within 1.5 ms of the one before as a main-thread stall delivers it, as the steps it merged. During momentum a bunched wheel is not a jump, so momentum no longer restarts a followed pan, and the steps after it no longer read as a lift. Not exported from the package entry point.
  • Internal: a pager for touch presentations that pages like a UIKit paging scroll view. A horizontal pan moves the pages one to one and rubber-bands at the ends. The release picks the page with UIKit's rule and settles on UIKit's paging curve on the compositor, and a finger can catch it mid-flight. It takes every pointer: a mouse drags it as a finger does, and its pan follows a trackpad's horizontal scroll, at most one page per swipe. A mouse wheel's scroll stays the page's. Its motion values are internal constants. Not exported from the package entry point.
  • Internal: UIKit's paging values and math for touch presentations, measured on iOS 26.2: the thresholds that pick the page a release settles on, the settle that carries it there and setContentOffset(animated:). The settle and setContentOffset(animated:) replay the recorded frames to under half a pixel. The unused projection rule (selectPage and scroll.paging) is gone, so the measured thresholds are the one paging rule. Not exported from the package entry point.
  • Internal: UISwitch's values measured on iOS 26.2 (its geometry, the springs of the thumb's lift, settle, travel and drag, the track colour, its minimum lift time and its flip distance) join the UIKit constants table as internal constants, with the rule a switch's drag follows as a pure function: the finger flips the switch once it has travelled the track width minus the thumb width from where it landed, coming back past that point flips it back, and lifting the finger commits the side shown, or toggles when nothing flipped. Not exported from the package entry point, and no theme sets them. Switch's touch presentation plays them.
Contributors
Thanks to everyone who contributed to this release: