What's New

Release notes and changelog for all packages.

0.7.12

Experimental APIs
  • Adds the English default name of the Lab ChatVirtualizer's own scroll container (@astryx.chatVirtualizer.label, "Messages"). It is a Lab string shipped in Core's locale file; it adds no public API to @astryxdesign/core. (#5461)
New Features
  • BottomSheet: at rest, a sheet's content starts below the grab bar whatever its padding, so the first line is no longer drawn through the bar's fade. The block-start inset is never less than the bar's height (--spacing-6): the band under the bar is not padding a child escapes, so a lone Section starts below the bar too; scrolled content still passes beneath it. A sheet at the default padding starts its content 8 px lower, one with padding={0} starts it below the bar, and one whose only child is a Section starts that Section 24 px lower and grows by the same amount. Core's own padding={0} sheets (the touch date and time pickers, the DropdownMenu and ContextMenu sheets, and the PowerSearch and Tokenizer sheets) no longer reserve that band themselves, so the pickers, PowerSearch and Tokenizer look the same and a menu's first row sits 8 px lower. The CLI's table-filter and table-inbox page templates drop their own band too, so it is not doubled. (#8558)
  • ChatLayout keeps its composer on top of the software keyboard where the visual viewport shrinks for it, instead of leaving it underneath until the browser scrolls the whole page. In Chrome on Android the dock rides Gboard's measured slides up and down, in step with the keyboard. In Safari on iOS (in the browser and as a home-screen app) and in Firefox for Android, it moves above the keyboard once the browser reports it. Where a page sets interactive-widget=resizes-content, Chrome shrinks the page for the keyboard itself and the composer stays above it without moving. A conversation at its newest message stays there, and the rest of the transcript can still be scrolled above the composer. On a touch screen, in a top-level page, every way into the composer's text (a tap, the keyboard's previous and next buttons, Tab, the input's focus()) reaches it without the page scrolling; under a mouse or inside an iframe the browser's own focus applies. In a top-level page on a touch screen, the composer's wrapper (without the scroll-to-bottom button) is a group with no name. When the keyboard's Done ends typing, focus rests there (it is no tab stop), so the next tap or Tab starts from the composer; it shows the focus ring after keyboard input only. A tap that focuses the composer still raises its click once. Under a mouse or inside an iframe, the wrapper is a plain container. Under Reduce Motion the composer never travels with Gboard: it cross-fades to its place above the keyboard. Under a mouse, with no software keyboard, nothing changes. The browser-support guide's section on the on-screen keyboard covers ChatLayout's composer. (#8176)
  • Kbd shows meta as ⌘ on Apple platforms, where it showed "META". (#10528)
  • Kbd shows ctrl, alt and shift as text ("Ctrl", "Alt", "Shift") off Apple platforms and before hydration, and meta as "Win" off Apple platforms and before hydration, instead of Apple's ⌃ ⌥ ⇧ symbols and "META". Apple platforms keep the symbols, and spoken names are unchanged. The text comes from the catalog, so other locales can translate it. (#10524)
  • A LayoutPanel that takes a useResizable region in its resizable prop slides closed and open from the edge facing its ResizeHandle when the region collapses or opens, under every pointer, with the content beside it moving on the same motion: through collapse(), expand(), Enter, a double-click, the grow arrow, a controlled isCollapsed, or a lift past the collapse threshold. A drag that reopens the panel follows the pointer, and Reduce Motion is honored. A hand-built ResizableProps object does not slide. No prop or option is added. (#9989)
  • On a phone or tablet, drag a Lightbox photo down to close the viewer, as in the iOS Photos viewer. The photo follows your finger and shrinks a little as you pull, while the backdrop fades and the controls fade faster. The backdrop fades without its blur, which comes back once it is at rest. Let go moving down, however short the pull, and the photo carries on down as the viewer closes. Flick it back up, or bring it back to where you started, and it springs back into place. A zoomed photo still pans when you drag it; the drag to close starts from the fitted size. Videos are unchanged. (#8215) The viewer's controls now sit in their own layers, which fade together during the drag.
  • A Lightbox gallery now pages the way the iOS Photos viewer does. On a phone or tablet, drag or flick between items: the row follows your finger, and the release lands on the next or previous item, one at most. A gap of 40 px separates the items while they move. A zoomed photo pans with your finger until it reaches its edge; a new drag from that edge moves to the next item. A photo you leave zoomed returns to its fitted size once the gallery rests. Under a finger, the previous and next buttons and the arrow keys slide to the item instead of swapping it in place. (#8197) Each item's caption moves with its item, right under its photo. onIndexChange also reports a swipe.
    Lightbox now loads its touch code with it, as Toast and Slider do. Its import grows from 51.4 KB to 99.6 KB gzip with the zoom and paging beneath, mostly shared touch modules that a page loads once; Lightbox's own code adds 14.1 KB minified.
  • List takes animatedLayout, the handle from useAnimatedLayout({containerRef}), and ListItem takes itemKey, the row's identity. With the handle, when rows are inserted, removed or reordered, an inserted row enters, a removed row (a swiped one with its action showing) collapses in place, and a row that crosses rows moving the other way rides above them with the surface color behind it, as an iOS table's opaque cell does. The rows after a change and the content after the list, up to the handle's container, glide to their new places. All of it runs on one shared motion and starts together, under every pointer; under Reduce Motion nothing travels. A row without an itemKey changes at once, and without the handle the whole list does. (#8106)
  • While a reorderable List row is in reorder mode, a hint anchored to its handle, in the keyboard hint's layer and theme roles, shows the moves and Done. Each is a button that does what its key does and leaves the focus on the handle, so a row can be reordered by taps alone: the handle, the moves, then Done. (#8139)
  • createReorderable({onReorder, isReorderable}) makes a collection's reorder behavior, and List takes it as reorderable: each ListItem with an itemKey gets a reorder handle at its end, and each committed move calls onReorder({key, to}) once, with the row's key and its index after the move. On a touch screen a finger held still on a handle picks up its row the way an iOS table's reorder control does (a flick on it still scrolls): the row stays in its place, dimmed, while a copy of it follows the finger and an accent line marks where it would land; the other rows stay still, the page scrolls near the edges, and on release the rows rearrange, gliding to their new places. A pen held on a handle picks up its row the same way where the primary pointer is coarse. A mouse, or a pen where the primary pointer is fine, drags a handle at once with the same copy and line, and rows take their places without motion; a cancelled drag puts everything back at once. Without a drag, a click, Space or Enter on a handle turns on reorder mode for its row: the insertion line marks the row's place, each arrow key moves it a place at once, announced with its place and neighbours, and Escape or another activation ends the mode, keeping the moves. The object's start(key) enters the same mode from the app's own UI, such as a row's context menu. A List without reorderable loads none of the reorder code. (#8139)
  • A ResizeHandle that any pointer pulls past the maximum, or under the minimum, of a region whose pane a LayoutPanel renders now moves the handle with resistance, at most about 8 px past the limit and over the content beside it, while the panes keep their sizes, and the handle springs back to the limit after the lift. A panel sized by the region's size alone stops at the limit. A collapsible region no longer collapses mid-drag: only the lift collapses it, when the pointer is past collapsedSize, or released fast enough to come to rest past it, and a LayoutPanel's pane slides shut on a spring from the release velocity. Any other lift under the minimum returns to the minimum. A pointer that grabs the handle again catches it where it shows. Arrow keys still stop at the limit. Reduce Motion lands both at once. (#10292)
  • Tables can window fixed-height flat data: pass useTableRowsVirtualization({rowHeight, initialViewportHeight}) to Table.virtualization. Table keeps the complete data and row identity, mounts only the rows in its viewport plus a few overscan rows, keeps native table semantics with full-table row positions, keeps the focused row mounted, and falls back to rendering every row for content or geometry it cannot window. Tables that do not opt in are unchanged. (#8280)
  • useTableRowsVirtualization's viewportHeight is renamed initialViewportHeight before the hook's first stable release. It only sizes the first window, on the server and before the viewport is measured; it no longer sets the Table's height. A windowed Table scrolls inside the height its parent gives it, so give the parent a height. rowHeight is unchanged. (#10894)
  • Table plugins can now read where a row sits. Table passes each body row and cell transform an immutable TableRowContext (the row's key, its zero-based logicalIndex in the complete data, the row and header counts, and the row model). It passes the scroll-wrapper transform a TableRenderContext with a stable viewport reference. A plugin declares rowModel: 'flat' when its body transforms keep one row per data item. useTableSelection and useTableStickyColumns declare it. useTableRowIndex() without options now numbers rows from the context (passing data still numbers from that array), and rows that move re-render only for plugins that read the index. Read context values during the transform; a later read from a callback warns in development. The CLI's numbered-rows block no longer passes data. (#10171)
  • Windowed tables stay windowed with row selection and row numbers. A windowed row-number column widens to fit its last number before that row mounts, at the table's font and density, and pinned columns after it move with it. (#10658)
  • Under the touch presentation, ToggleButtonGroup tracks a finger's or a pen's press across its toggles, like a menu. Press a toggle and slide across the others: the highlight follows, and only the toggle you lift on changes. Lifting outside the group changes nothing. A mouse press is unchanged: it acts as a native toggle's, on the toggle it began on. With a finger, a toggle the group tracks keeps its 44 px target, now drawn by the group. A toggle without a value keeps its own press, and the keyboard is unchanged. Before, each toggle tracked only its own press, and sliding off it changed nothing. An enabled ToggleButtonGroup 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. (#8660)
  • Under a coarse primary pointer, expanding a TreeList row glides the rows below it to their new places on the shared layout glide while its children fade in on the same timing, so the tree moves as one. A collapse fades the children out as the rows below glide up, and the chevron turns on that timing. The rows used to appear and leave in a single frame. Without an animatedLayout handle the motion stays inside the tree, so content after the tree takes its place at once, and the tree clips its bottom edge while it moves so no row paints over that content; pass a handle for it to glide too. The guide lines beside a group now show and hide with its rows. With reduced motion on and a finger, the children fade in where they land. With a mouse the rows still change at once. Under every pointer, a guide line now ends at the last row it joins instead of running on beside an expanded last row's children. (#8088)
  • BaseTypeahead takes menu, which chooses what its anchored menu shows while Astryx keeps the layer: its position, top layer, outside press, Escape, focus return and ARIA. {role: 'listbox', render} places information such as a header or a key hint around the result list, and anything a person acts on stays a result, so the arrow keys reach it (a control outside the list warns in development). {role: 'dialog', label, render} shows content that takes focus in a dialog named by label; closing it returns focus to the element focused when it opened, or to the input. A new handleRef exposes open() and close(), and onOpenChange reports each change; there is no controlled open state. Calling open() from onChange keeps the menu open, so a pick can switch the list to a dialog on the same layer. Typeahead forwards menu and handleRef. (#10544)
Fixes
  • a month position past the end of a Gregorian-aligned calendar's year constrains to that year's last month in calendarMonthFromYearMonth and useCalendarDays, instead of returning a NaN CalendarMonth and laying out the next year's January (#10461)
  • Declare renderer-owned DOM boundaries so decorator overlays mount outside managed content without changing safe inline hosting. RichTextEditor also mirrors its dir prop onto the wrapper around the editable surface, so the editing surface and its content blocks, the placeholder, UI rendered through plugins, and relocated overlays follow dir; the editing surface previously kept the surrounding direction. (#7633)
  • On Android, text follows the reader's system font scale in every theme with no setup, in browsers that report env(preferred-text-scale) (verified on Chromium and on Chrome stable). The root Theme reads env(preferred-text-scale) and scales every font size by it, as it already follows Dynamic Type on iPhone. Before, the system font scale reached Astryx text only when the page added <meta name="text-scale" content="scale">. A page with content="scale" keeps working as it did: its root font size carries the scale, and the root Theme adds none. Browsers without either see no change. astryx docs typography/type-scale describes it. (#10727)
  • Motion: in WebKit on Linux, the last frame of an animatedLayout change shows where each motion ends once a frame has drawn the motion near its end. Under load, that frame, and every frame of a long task over its end, could show a glide, an exit's fade or an indicator's turn part of the way through: a collapsing TreeList drew the rows below 44 px back, its leaving rows half faded and its chevron mid-turn. A long task that starts before that frame, or a motion near its end only at its last keyframe, can still show it. At normal speed the motion is unchanged. (#10663)
  • Motion: a Switch's value change mid-travel keeps the thumb's running speed. A rebase toward the new rest shifts the curve whole. (#10369)
  • Avatar: initials are drawn as generated content with empty alternative text instead of text, so axe's Label in Name check (label-content-name-mismatch) no longer flags a link or button avatar that shows initials. The accessible name, the name tooltip and the initials' appearance are unchanged. (#10816)
  • Under reduced motion, a BottomSheet that a finger's swipe dismisses fades out where the finger left it. Before, it jumped back to its open position in one frame and faded from there. With motion, the next open after such a swipe rises from below the screen again, instead of starting where the finger left the sheet. (#10925)
  • BottomSheet: a drag reads its release velocity from Core's velocity tracker, on each event's own timestamp, also when a touch drag starts on the sheet's content. The release depends on the last two moves, so a move that reaches the page late earlier in a flick no longer slows the flick. A hold weighs on the first move after it, as iOS's filter does. Two rules differ from iOS: a finger that holds still for more than 40 ms before the lift releases nothing in motion, and a release needs two moves. (#10463)
  • A stacked BottomSheet whose close waits in a suspended transition takes over the dim when the sheet beneath it closes, so the page behind it stays dimmed. (#10776)
  • BottomSheet: an open sheet that renders again no longer reads the viewport height. It keeps the viewport height that its resize listener reads, so a tap that renders the sheet again forces no style recalculation or layout in React's commit. The sheet's height, reserve and detents are unchanged. (#10363)
  • Button: disabled buttons no longer render the native disabled attribute. They stay focusable in keyboard tab order, keep focus when they become disabled while focused (a link Button, which becomes a <button> when disabled, still moves focus), and expose aria-disabled="true". All activation paths (mouse clicks, Enter, Space) and clickAction/onClick callbacks remain blocked without losing focus to the document body. A disabled named submit Button withholds its name so new FormData(form, submitter) omits its value. A ButtonGroup whose members are all disabled (whether on the group or individually) keeps its one Tab stop instead of dropping out of the Tab order or giving every member its own stop, and Carousel's hidden scroll buttons are never Tab stops. Tests that assert toBeDisabled() or :disabled should query [aria-disabled="true"] instead. (#7906)
  • A labelled Button grows with its label when the text size grows: its height is its size, or one line of its label when that is taller, so the label stays inside the button. At the default text size Buttons render exactly as before, a caller's height still applies, and icon-only buttons keep their fixed square. (#10588)
  • Calendar day buttons grow with their numbers when the person's text size grows, such as a larger browser default font size. Their size is now a minimum, so a day's number stays inside its own tap target and a tap no longer lands on the day below. At the default text size nothing changes. (#10596)
  • Under snap paging (hasSnap={useSnapPaging()}), Carousel's edge buttons and handleRef's scrollNext, scrollPrev and scrollTo move the row through the paging, also from rest. A touch that catches such a move now leaves the row on a page, as a flick's settle does. On iOS a still touch used to stop the browser's smooth scroll between two items. (#10384)
  • Under snap paging (hasSnap={useSnapPaging()}), Carousel's edge scroll buttons and edge fades follow the row as it moves. They change in the frame where it leaves an edge. A flick used to leave them as they were until the settle ended and the row went back to native scrolling, so the start button came back about half a second after the row had visibly left the start. (#10359)
  • ChatComposerInput: composing with an input method (for example Japanese or Chinese) right after picking a mention, inserting a token, or inserting text after a token now commits only the composed text. The composer places its caret inside the trailing text, not on an element boundary, so the first raw letter of the composition is no longer committed. Right after a mention pick, one Backspace now removes the mention with its space, and no stray line break is left. (#6423)
  • ChatLayout's scroll-to-bottom button now appears when scrollRef names the document's scroller and the reader scrolls the page up. The stream scroll also stops following there, so a streaming reply no longer pulls that reader back to the newest message. (#10779)
  • ChatLayout with a scrollRef now rests the newest message above the fixed composer dock at the scroll's end. The message area's end padding holds the dock's height and follows it as the composer grows. (#10676)
  • useChatStreamScroll's scrollToMessage now puts the message at the top of the viewport when the scroller is the page itself. It landed off by the page's own scroll. (#10781)
  • CommandPalette stays open with no results when a search or bootstrap request rejects (#10675)
  • A Table, or a List with edge="bleed", that is the first or last child of a rounded Card or Dialog that holds no other Table or bleeding List deeper inside now rounds with the corner it reaches, so the table's focus ring stays whole at the container's corners instead of being cut off. A bleeding List with a header rounds only its last row. Every other corner stays square: standalone, inside a square container or a wrapper element, between other content, at the top of a BottomSheet (below its grab bar), or while another Table or bleeding List sits deeper in the same container. (#10586)
  • CodeBlock's "Failed to copy value to clipboard." announcement now uses the assertive live region instead of the polite one, as status announcements require for errors, so screen readers report a failed copy right away. A successful copy is still announced politely. (#10448)
  • A swizzled Outline (or another copy that carries Core's Markdown plugin protocol) now type-checks against the package's Markdown plugins: MarkdownPluginEntry and MarkdownTransform carry their node type on a shared, versioned key instead of a module-local symbol, so the package's and the copy's types match. The member exists only in types; runtime trust and claim checks are unchanged. No API changes. (#10641)
  • A swizzled copy and the package now agree on the animated-layout handle, code-language values and snap paging. A handle from useAnimatedLayout passed to a swizzled AppShell, List, Table, TreeList, Collapsible or SideNav no longer throws when the layout changes, and those copies type-check: each brand is read through a registered, versioned key at runtime, and the types carry one optional brand member that is never present. No API changes. (#10576)
  • Core registers every React context, and the English its components register, under a versioned key, so two copies of Core's modules on one page share them: a provider from one copy reaches consumers from the other, a layer boundary from either resets the layer-scoped contexts of both, and a component from either shows its English. A copy built against another version of a context keeps its own. No API changes. (#10233)
  • A swizzled component that carries Core's touch code, such as a swizzled Switch or Slider, now joins the package's gesture host, window input listeners, click guard, layer input holds and moving-element hit testing for the page instead of keeping a second set, so the copy and package components do not both claim the same touches. No API changes. (#10599)
  • A swizzled List, TransferList or ListInput and the package now agree on a createReorderable object: its reorder machinery is read through a registered, versioned key. Before, a swizzled List found no machinery on an object from the package and showed no reorder handles. No API changes. (#10741)
  • A DateInput or DateTimeInput with presentation="bottom-sheet" no longer causes a hydration mismatch when the server and the browser are on different dates. The closed sheet's calendar now renders right after hydration, once the browser's today is known. (#10400)
  • Dialog: under React StrictMode, a Dialog with a DialogHeader that is first mounted open and then removed while open (rendered only while open) now returns focus to the element that opened it, instead of leaving focus on the page body. The opener is captured only on the closed-to-open edge. (#5642)
  • Dialog: a DialogHeader title now takes focus only after the dialog is modal, also when the header mounts in the render that opens the dialog. When no other control asks for focus, initial focus now starts on the title in every browser. Before, a header with a start control, and any header in Firefox, started on the first control. (#10408)
  • Drawer: a non-modal drawer (hasScrim={false}) that unmounts while it is open, for example one rendered only while open ({isEditing && <Drawer 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. A modal drawer already did. (#9672)
  • DropdownMenu: a finger's hold-slide-lift no longer flashes the focus outline on the menu button. When a held press opens the menu, the button takes focus first, so focus can return to it when the menu closes; that focus now shows the outline only after keyboard input. A keyboard open and close still show the outline on the button. (#10079)
  • Dialog, CommandPalette, BottomSheet, Lightbox, Drawer, MobileNav, Popover: Tab no longer escapes a modal through a radio group. The browser gives a same-name group of native radios one Tab stop: its checked radio, or, when none is checked, its first moving forward and its last moving backward. The focus region now finds its first and last stops the same way. Before, Tab from a group's checked radio left the modal for the browser's toolbar when the group ended the modal and that radio was not last in it, and Shift+Tab did the same when a group started it. Reported by @duytbp. (#10304)
  • Gestures: a finger's lift is read on the clock its moves came on. In WebKit on Linux, a page pointerup listener that runs long no longer makes a fast flick read as a resting finger, or a tap lifted in time read as a long press. (#10583)
  • HoverCard and useHoverCard no longer open on keyboard focus of the trigger while isOpen={false} is passed. The controlled false already refused hover, but tabbing onto the trigger opened the card and reported onOpenChange(true) against the owner's state; focus now takes the same refusal as hover. (#10181)
  • HoverCard: a labelled card no longer puts aria-haspopup="dialog" on a role-less trigger, such as text or a <time>. Such a trigger names the open card through aria-controls only; a button or link trigger still gets aria-haspopup and aria-expanded. (#10733)
  • A HoverCard rendered into another document, such as an iframe or a Picture-in-Picture window, now closes when Escape is pressed there, and Escape from inside the card returns focus to its trigger. Moving focus from the trigger into such a card also keeps it open. Before, the card read only the page's document, so Escape in the other document never closed it. The card now also ranks on the shared dismissal stack by its trigger's place, so a card whose trigger sits inside a focus-trap container takes Escape before that container, as the topmost layer. (#9592)
  • HoverCard and Tooltip: a controlled isOpen={true} (or isDefaultOpen) no longer strands the layer in the viewport corner when its trigger mounts with no layout box yet, for example inside a Dialog that has not called showModal() yet. (#5398) Dialog mounts its children before it opens (isOpen gates showModal(), not rendering), so a HoverCard or Tooltip inside one with a controlled isOpen={true} runs its show effect while the trigger sits in a still non-modal <dialog> and has no box. A trigger with no box is not a valid CSS anchor: the popover resolves to its fallback position in the viewport corner, and unlike a live layout change that resolution is not revisited once the trigger later gets a box.
    Layer's show() now opens immediately when the trigger already has a layout box (an empty one, such as a ContextMenu's cursor anchor, counts), so a menu or popover still opens in the same task as the press that asked for it. Only a trigger with no layout box (display: none, or inside a <dialog> that is not showing) waits: first for it to get a layout box and for its dialog to show, then for any running animation on the document timeline that ends on its own, on the trigger or an ancestor, to finish, so the layer anchors to the trigger's settled position and not to a mid-transition one. Paused, infinite, and scroll- or view-driven animations are not waited on.
    The box wait is driven by signals and polls nothing: a ResizeObserver for a trigger that gains a layout box, an IntersectionObserver for a purely display: inline trigger (such as the wrapper <span> of a text-only trigger), which a ResizeObserver never delivers an entry for, and the enclosing dialog's open attribute and toggle event. A dialog counts as showing when it is open or shown as a popover, so triggers inside a non-modal Drawer still open their layers. The wait has no time limit and ends when the trigger gets a box inside a showing dialog or the open is cancelled (a later show() or hide(), or unmount). If the trigger element is replaced while waiting, the wait restarts on the new one, and a trigger that unmounts for good stops observing. Without a layout engine to wait on (no ResizeObserver or no Web Animations API, as in jsdom) the layer opens immediately.
    A transient null then same-element call on the trigger ref, as a combined ref utility makes when a handler changes identity, no longer removes and re-adds the element's anchor-name, which could also leave an open layer stranded in the corner.
  • Layers with an entrance input hold: a finger or pen that was already down when a light-dismissing layer opened, and lifts while it enters, now lifts through the hold's shield onto what is under it in WebKit, so the layer dismisses as it already did in Chromium. The shield leaves a small opening at each such press until it lifts. New presses during the entrance are still held. (#10398)
  • Layer: a light-dismissible layer that opens from a right click's contextmenu event stays open when that same press is released. Before, the release counted as a press outside, so a DropdownMenu opened through isMenuOpen from a right click closed at once. A later press outside still dismisses the layer. (#10128)
  • A popover taller than the room on both sides of its trigger keeps its top when the keyboard shortens it. The field being typed into stays under the caret. It used to jump below the trigger as the keyboard arrived, and back as it went. (#10497)
  • Once the keyboard caps a layer such as a popover, a scroll a person starts in it afterwards is no longer undone. On a busy page, the layer could scroll back to the focused field just after. A later keyboard change still brings the field being typed into back into view. (#10457)
  • A Tooltip, including a Slider's value bubble, no longer jumps to another side of its trigger in the middle of a scroll. Before, when a scroll carried the trigger toward the edge, the layer runtime took the Tooltip out of rendering for one forced layout so the browser would choose its position again, and it did this again on later frames of the scroll. Now the Tooltip has one fallback list from the start, and no option in it covers the trigger: it tries the opposite side first, then beside the trigger, then a side sized to the room. During a scroll, the Tooltip keeps its side: it is not checked or placed afresh until the scroll stops. In the first frame painted after the scroll stops (at scrollend, or 150 ms after the last scroll event where the browser has no scrollend), it is checked once and moves to the side with room if it needs to. At a show, a remount or a size change it is checked as before. (#10439)
  • A Tooltip's content scrolls by CSS alone, and nothing watches its trigger move. A Tooltip now has overflow-y: auto from its first frame, with no overscroll containment. It scrolls only while its content overflows, so a wheel over a Tooltip that fits still scrolls the page. Once a tall Tooltip has scrolled to its end, the next wheel moves on to the page, where before the page held. A Tooltip is now always a scroll container, so position: sticky and scroll(nearest) timelines inside its content resolve against the Tooltip. The layer runtime no longer reads the Tooltip's scroll size after its trigger moves, and it no longer observes a trigger that moves without resizing. (#10472)
  • A swizzled LayerProvider now shows the package's toasts: the viewport the package's Toast registers renders in a copied provider's outlet, and the package's provider renders a copy's. Before, each copy kept its own registry, so toasts added under a swizzled provider never showed. The registry lives under a registered, versioned key. No API changes. (#10800)
  • Layout: a false, true, or empty-string slot, such as false from isOpen && <LayoutPanel />, now counts as empty. The neighbouring regions move out to the layout edge, the same as when the slot is omitted, and with contentWidth a closed side panel no longer stops the content area at the content-width frame. The docs now list children and ref, show how to hide a region, and say that landmark roles go on the region components. (#10500)
  • LayoutContent: the edge away from a single start panel now takes the Layout-edge inset, so padding={0} on the Layout makes it full bleed, and with contentWidth its children end one Layout-edge inset inside the content-width frame, as they do without panels. Each edge now publishes the padding it applies, so a full-bleed child such as a Table lines up beside an end panel and under a header without a divider. A Layout nested under a header or footer without a divider keeps its own content spacing instead of taking the outer collapse. (#10516)
  • A Layout with no contentWidth no longer caps its LayoutHeader and LayoutFooter at the viewport's width. In a frame wider than the viewport, such as a scrolling canvas or a wide embed, their content now spans the frame like the rest of the Layout. (#10715)
  • LayoutFooter: a data-divider attribute passed by the caller no longer replaces the divider state the footer reflects, so the content above a footer without a divider keeps its collapsed spacing, and a footer with a divider keeps its spacing above the line. The docs now list padding and ref, and say that an unset hasDivider follows the Layout's defaultHasDividers. (#10674)
  • LayoutHeader: a data-divider attribute passed by the caller no longer replaces the divider state the header reflects, so the content below a header without a divider keeps its collapsed spacing, and a header with a divider keeps its spacing below the line. The docs now list padding and ref, and say that an unset hasDivider follows the Layout's defaultHasDividers. (#10686)
  • LayoutPanel: on an edge that takes the Layout's own inset, the panel now tells its children the padding it applies there. Children that read their container's padding, such as a full-bleed Divider, Table, or TabList, or a nested Layout, now follow the panel's outer edge whenever the Layout's padding differs from the inner inset. Before, they used the inner inset: with padding={6} a full-bleed Divider stopped 8px short of the edge, and with padding={0} it ran 16px past it. The docs now say which edge hasDivider draws on, that the Layout's defaultHasDividers does not apply, and that padding={0} is full bleed, and they list ref. (#10774)
  • Lightbox: a screen reader now hears the viewer's own messages while it is open. Moving to another item ("Mountain lake, 2 of 4") and zooming in or out are announced inside the open viewer; before, they went to the page behind the modal viewer, where a screen reader does not read them. The 0 key now returns a zoomed photo to its fitted size. The docs list the 0 key, and no longer say that the lightbox is only for images. (#10775)
  • Lightbox's drag to close now plays at the theme's tempo, like the viewer's other motion. At the default tempo it plays exactly as before. (#10630)
  • An open Lightbox shows the nearest item when index or defaultIndex is NaN or a fraction between the first and last item. A fraction rounds to the nearest item, and NaN shows the first item. Before, the viewer rendered nothing for those values. (#10632)
  • A reorderable List in its own scroll box keeps the dragged row under the pointer when a wheel during a mouse or pen drag scrolls the page, as a wheel at the box's end does. The wheel scrolls as before. (#10742)
  • Markdown: each paragraph, heading, quote and list item lays out in the direction of its own text. A Hebrew or Arabic paragraph in a left-to-right page now starts on the right, and an English paragraph in a right-to-left page starts on the left. A block with no letters, such as digits, punctuation or an image, takes the page's direction from the InternationalizationProvider, also inside a quote or list item that reads the other way. Lists, code blocks and tables keep the direction around them too, and the text in each table cell reads in its own direction. A numbered item that reads against its list shows its number beside its own text, and a table cell that reads against its table keeps the table's column lines and any explicit column alignment. A task list now keeps to the same prose width as other lists. (#10293)
  • Menus: the arrow keys, Home, End and type-ahead now reach a disabled row in DropdownMenu, its sub-menus, MoreMenu, ContextMenu and NavHeadingMenu, so a keyboard or screen-reader user finds the row and its description. The row takes focus, is announced as disabled, and Enter, Space or a click on it still does nothing and leaves the menu open. Opening a menu from the keyboard still lands on an enabled row. (#10160)
  • DropdownMenu: a held mouse dragged from the trigger onto a row keeps that row lit. On a loaded page the menu's open focus could land after the drag reached the row and take the highlight back to the menu container until the pointer moved again. (#10590)
  • DropdownMenu: a menu that a mouse press opens stays open when that press is released quickly away from the trigger, or after the trigger moved away under the pointer. Before, the browser's light dismiss read that release as a press outside and closed the menu at once. A press released after the settle time outside the menu still closes it, and a later press outside dismisses it. (#10689)
  • Under a finger, the month and year wheels behind the calendar title in the DateInput and DateTimeInput bottom sheets now behave like the iOS date picker's: (#8209)
    • Turning a wheel moves a chosen date to the new month and keeps its day, so October 15 becomes May 15. A day the month lacks becomes its last day, the result stays within min and max, and DateTimeInput keeps the time. A date that dateConstraints refuses is not chosen; the calendar still moves.
    • With no date chosen, the wheels only move the calendar.
    With a mouse, the wheels still move only the calendar.
  • Motion: elements that start moving from rest in the same frame now start at one time. Before, each element took its own reading of the clock in that frame, so items starting together, such as a carousel's pages as they settle, could start apart by as long as the frame callbacks between them ran. (#10584)
  • Motion: a spring retarget that the browser commits late, behind a busy main thread, now starts at that frame, from where the element is on screen. Before, it kept the clock of the call, so the element jumped to where the new curve had got to: 42 px back in one frame for a retarget behind a 200 ms block. Motion calls made in one callback now share one clock, so the children of a pager line up after a retarget. A retarget made inside a page's own frame or ResizeObserver callback now shows its new curve one frame later. (#10607)
  • MultiSelector: opening the closed list never highlights a disabled option. ArrowDown, Enter, Space and a press highlight the first enabled option in the order the list opens in, and ArrowUp the last, so Enter no longer lands on an option it cannot toggle. A list with search still highlights nothing when a press or Enter opens it. (#10820)
  • Carousel paging: a finger or a pen that lands on a row still settling after a swipe no longer reaches the item under it: no press highlight and no click, as on iOS. A mouse click is unchanged. (#10370)
  • Carousel paging: a finger or a pen that lands on the row during an edge button's move now stops it at the touch, as on iOS, instead of letting it run on for about 85 ms. The item under the finger still takes the tap. A mouse is unchanged. (#10545)
  • A page that a swipe releases now settles at the theme's tempo, as the rest of its motion does: in a Carousel given hasSnap={useSnapPaging()}, and in a Lightbox gallery. At the default tempo the settle is unchanged. (#8197)
  • Pagination's ellipsis grows with a larger text size, as its page buttons now do through Button. Its size is now a minimum height, so the "…" stays inside its own box. At the default text size nothing changes. (#10567)
  • Pagination wraps its row when its controls don't fit, as at a larger text size on a phone, instead of scrolling the page sideways and pushing Next off-screen. Previous stays first and Next stays last. Beside other content in a flex row, Pagination can now shrink to its widest control and wrap at the default text size too, where it held one line before; give it flexShrink: 0 through xstyle to keep one line there. (#10552)
  • parseColor answers null for constructor and __proto__ (in any case), as for any unknown name, instead of a truthy empty RGBA that made composed callers such as chart colors.alpha return rgba(NaN, NaN, NaN, …) (or #NANNANNAN at full opacity) instead of the original string (#10468)
  • A closed Popover, and any usePopover composition, no longer leaves a hidden role="dialog" with its label in the DOM. The surface stays mounted but carries the dialog role, name and aria-modal only while open, so [role="dialog"] selectors and tests that include hidden elements find no dialog that is not on screen. The accessibility tree already omitted the hidden surface. Reopening restores them. (#10487)
  • A dialog Popover starts focus on its first enabled tab stop. It skips a disabled control, lets an element that holds tabindex="-1" yield to a later tab stop, and starts on its labelled surface when every control is disabled. Before, a DateInput or DateTimeInput calendar whose range starts in the shown month opened on the disabled Previous month button. Now it opens on Next month, or, in a one-month range, on the selected day, else today, else the first enabled day. Disabled controls stay reachable by Tab. (#10503)
  • Under a finger, Popover's growth shows its content from its first frame. The growth starts at opacity 0.001 rather than 0: Chromium skips drawing a layer at exactly 0, so the first frames of a growth from 0 showed the popover without its content. No 8-bit pixel differs from transparent at 0.001. (#10757)
  • In PowerSearch's phone sheet, a date range is now picked on a calendar inside the sheet, instead of a calendar popover opening over it. The desktop editor popover is unchanged. (#10618)
  • PowerSearch's phone sheet now edits single and multiple choices with the standard RadioList and CheckboxList at their usual spacing, instead of its own 48 px rows, and its Operator radios put the radio at the start of the row, as every RadioList does. The choices use the shared touch band, so their touch targets are smaller than before. End, Home and Enter no longer pick a choice; the arrow keys and Space work as in any RadioList or CheckboxList. Adds a "Sheet presentation · realistic config" story that covers every value type. The desktop editor popover is unchanged. (#10608)
  • PowerSearch: a filter token's field and operator now come from one catalog message (@astryx.powersearch.token.fieldOperator, "{field}: {operator}" in English), and its full text, which also names its remove button and editor, joins that label and the value with another (@astryx.powersearch.token.labelValue, "{label} {value}"). A locale can reorder the parts and change the punctuation. PowerSearchToken uses the same message. English tokens read as before, except that a filter with no operator text no longer shows a trailing colon. (#10437)
  • Press feedback: a pointerup that carries no pointerId, such as a bare event a test helper or drag script dispatches, no longer throws Cannot read properties of null (reading 'live') when no press is held. It is ignored, as pointercancel already does. (#10695)
  • Inside a scroll view, a pressable's highlight now comes 150 ms after the touch, even when a busy page handles the touch late. Before, the wait started when the page handled the touch, so the highlight came late by that delay. This covers every pressable, and SegmentedControl, Switch, Slider and usePressTracker controls, in a scroll view. (#10260)
  • A theme duration token written with calc() now times a press's release as the browser resolves it. Before, the release clock fell back to 175 ms while the fade played the token's value. (#10069)
  • Two loads of Core's scroll-lock modules on one page now share one page scroll lock: closing the overlay that opened first no longer unlocks the page while the other overlay is still open. Text-selection locks, which a swizzled copy carries, are shared the same way, so a copy's release no longer restores a selection lock the package still holds. No API changes. (#10822)
  • useScrollableArea: an ancestor's inline style change measures the scroll area again only when it changes the axis mapping or the boxes' existence (direction, writing-mode, display, visibility, content-visibility); a size change still reaches it through the resize observers. A BottomSheet writes its transform, and its scrim's custom property, on every input sample of a drag, and each write forced a full measurement (its computed-style reads and the scroll geometry) in the next frame, a style recalculation and a layout on every frame of the drag. (#10034)
  • getContentProps from useScrollableArea now applies a caller's xstyle instead of leaking it to the DOM. (#6314) A viewport that lost overflow while focused drops its leftover tabindex as soon as it is blurred, and a focused viewport in another document keeps focus when it loses overflow. ScrollableArea's viewport also sheds the obsolete -webkit-overflow-scrolling and initial-value scrollbar declarations.
  • Selector: when the options move or reload while the list is open, the highlight stays on its option instead of naming whatever option now sits at its old position. If its option leaves, the highlight moves to the next remaining enabled option after it, or the previous one when none remains after it, and with none left nothing is highlighted. (#10818)
  • Selector and useCombobox: opening a closed list starts on the selected option, as the WAI-ARIA listbox pattern asks, and never on a disabled option. Before, ArrowDown and ArrowUp opened on the first or last option even when it was disabled, and ArrowDown then Enter changed "Hard" to the first option. Now opening highlights the selected option when it is enabled. Otherwise ArrowUp opens on the last enabled option and ArrowDown, a press, Enter or Space on the first; with no enabled option nothing is highlighted. A search list opened by a press, Enter or typing still highlights nothing. MultiSelector is unchanged. (#8868)
  • A Selector whose trigger sits near the bottom of the screen now opens its list on screen. The selected-item overlay's clamp did not count the layer's viewport gutter, so near the bottom edge the browser flipped the list below the viewport and its last options could not be reached. (#10697)
  • In a searchable Selector or MultiSelector, typing now clears the highlight, so Enter never picks an option you did not highlight. Before, the highlight kept its old position, which could point at a different option of the filtered list or at nothing. ArrowDown then starts at the first row: the first enabled match in Selector, and Select all or the create row when shown in MultiSelector. (#8871)
  • Selector with hasSearch: a required field no longer puts aria-required on its trigger, a button where the attribute is not allowed. The search field carries it while the list is open, and the closed trigger still announces "Required", through the field label or, when the label shows no marker, through its description. (#10878)
  • SideNav no longer adds space below a footer when it has no footerIcons and no built-in collapse button. The sidebar rendered an empty footer row there, and the gap of the sticky bottom area added space after the footer. The row now renders only when it holds the collapse button or footerIcons, as the drawer already does. (#10721)
  • Navigation rows grow with a larger text size. The shared nav item styles (navItemStyles, used by SideNavItem and by TopNavItem and the mega menu in the mobile drawer) now take their size as a minimum height instead of a fixed one, so above 200% text a row's label no longer overlaps the next row, and its end content (such as a count Badge) stays inside the row. Collapsed rail rows keep their fixed square. At the default text size, TopNav drawer menu and mega menu rows with a description now fit their text instead of overlapping the next row; other rows are unchanged. A caller height on these styles no longer brings a row below its size; override minHeight instead. (#10550)
  • Carousel snap paging: a stop that sits within half a step of the row's end is part of the last page, so a flick, a wheel or a key never rests a pixel short of the end, and a step back from the end moves a full step. (#10591)
  • Carousel paging: a row that narrows while a finger holds it now rests where the row ends, instead of short of its end by as much as it narrowed. (#10425)
  • Carousel paging: while the paging holds a row, the pager measures its pages and travel from the row's layout, as at rest. (#10860)
  • A Step keeps its own aria-current over a caller's. Before, an aria-current passed to a Step replaced the reflected value, so a step that was not in progress could be marked current and the in-progress step could lose aria-current="step". Now only the in-progress step carries aria-current="step", whatever the caller passes. No API changes. (#10640)
  • Under a mouse, a key that cannot scroll a DateInput, TimeInput or DateTimeInput wheel, as Tab, no longer ends the wheel's key step. On a busy page, Tab right after an arrow key could commit the row the wheel was leaving. (#10924)
  • Table's column settings plugin keeps its active columns in state. When the table re-renders on its own after a render React discards, such as a suspended transition, it shows the committed columns. (#10911)
  • Table: three of its keyboard tab stops draw the theme's focus ring instead of the browser's default: the scroll wrapper once the table scrolls inline, and the tree plugin's row expander and expand-all toggle. A theme's --focus-outline-* tokens now reach them. The scroll wrapper's ring sits inside its box, clear of a bordered Card's border, so a Card no longer cuts off its edges (a Card's rounded corners still trim the ring's square corners); at density="compact" the tree toggles' ring sits inside the toggle, so the row does not clip it. The row-expansion, grouped-rows and filter buttons are unchanged. (#8873)
  • Table: a row expansion panel with panelVariant="muted" now paints its wash on its cell, so with an animatedLayout handle the wash slides in with the panel's content. On iOS Safari the panel's edge trailed the rows gliding below it for a few frames; now they stay together. At rest the panel looks the same. (#10403)
  • A Table column-resize handle now announces its column's rendered width from the first render after layout, and its announced range always holds that width, also when the layout renders a column past its maximum or minimum width. Before, until a column was first resized, its handle announced the column's minimum width, so a screen reader read the wrong width. (#10593)
  • A Table column-resize handle on a column with no maximum width now announces a maximum at or above its value, so a screen reader no longer reads the width past ARIA's default maximum of 100. It uses the window's width as the stand-in maximum, as an unbounded Resizable region does, and announces its value in words, for example "133 pixels". A column with maxWidth is unchanged. (#10577)
  • A Table plugin's transformScrollWrapper className now reaches the table's scroll container beside the wrapper's own class; before, the wrapper replaced it. (#10702)
  • TableTree rows no longer carry aria-expanded, which is valid on a row only in a treegrid. Each row's expand and collapse button still exposes its expanded state, and rows keep aria-level for their depth. (#10538)
  • A swizzled Table now honors virtualization from the package's useTableRowsVirtualization, and the package Table honors a capability from a swizzled copy. Before, each copy recognized only its own capability, so a swizzled Table rendered every row and its code failed to type-check. The capability is read through a registered, versioned key, and its type carries one required brand member that is never present at runtime, so only the hook makes a capability. A virtualization value the hook did not make now gets its own development warning. No API changes. (#10798)
  • TabList tabs, including a TabMenu tab, grow with a larger text size. Their size now sets a minimum height instead of a fixed one, so at 200% text and above a tab label is no longer clipped. At the default text size nothing changes. (#10534)
  • TextInput, TextArea, NumberInput, DateInput, DateRangeInput, DateTimeInput, TimeInput, Tokenizer, Typeahead, PowerSearch, ChatComposer and RichTextEditor: when the primary pointer is coarse (a phone or tablet), the focus look shows at once, with no fade, so a tapped field repaints once while the keyboard rises. With a fine primary pointer, such as a mouse, a click and the Tab key keep the fade. ChatComposer's focus depth also shows at once under reduced motion, as the other fields' focus look already does. (#10611)
  • TextInput: the clear button now runs changeAction with the empty value and shows the optimistic empty value and busy state, as typing does. The clear goes through the input's own change handler, so onChange and changeAction receive a real change event (before, onChange received null as its event and changeAction did not run), onChange runs first, and its preventDefault() cancels the Action. (#6425)
  • A truncated Text or Heading mounts its tooltip on the first hover, tap or focus, not as soon as it renders, so a long table or list of truncated cells mounts no closed tooltip layers at load. The hover delay, the tap and the focus rules are the tooltip's own: a touch that becomes a scroll opens nothing, and a tap outside closes it. No visual change. (#10290)
  • Theming: a theme's :active override now follows the touch press model. With a mouse it still paints on :active. Under a finger it paints only while Astryx believes the press, so a themed control no longer flashes the theme's press color on the touch itself or while the page scrolls. (#10420)
  • In Safari on iPhone, text follows the reader's text size (Dynamic Type) in every theme, branded included. Where the browser exposes that size through font: -apple-system-body, as Safari on iPhone does, the theme's font sizes scale with the size the reader picked in Settings (Display & Text Size, then Larger Text), each size on the curve of the iOS text style it plays: body text like Body, heading-1 like Title 1, display text like Large Title, with every role kept in order. A semantic size a theme fixes at a length, such as the 0.75rem supporting text of Butter, Stone and Y2K, scales on the curve of the step it reads by default. At the default size every font size is the theme's own; the family, spacing, line-height ratios and the root font size never change, text inputs keep their 16px floor on iOS, and browsers without the keyword see no change. There is no option, prop or document attribute: the root Theme reads the reader's size from a hidden element. astryx docs typography/type-scale describes it. (#10416)
  • Theme keeps its runtime-injected CSS in the document until the last mounted Theme using that theme unmounts. Before, the Theme that injected the CSS first owned the shared <style> tags, so unmounting it (a nested Theme around a dialog that mounted first, for example) stripped the component overrides and prose defaults from every other Theme still using that theme. Built themes, which import their CSS as a file, are unaffected. (#10178)
  • TimeInput shows the stepped time after an arrow-key adjustment made while a typed draft is pending, and leaving the field keeps that step. Before, the text typed before pressing ArrowUp or ArrowDown stayed in the box while the committed value and the screen-reader announcement had moved on, and blurring re-parsed that stale text and committed it over the step, silently undoing it. (#10179)
  • Timestamp exposes its details popup on the focusable time element. (#6298)
  • Toast: the viewport is each toast's only announcement owner. While an open modal hosts a top-layer viewport (the default), it announces each toast through that modal's own live regions, so a toast shown over a Dialog is announced once. Elsewhere it announces through the shared channel. A viewport rendered in place announces through useAnnounce, which delivers inside an enclosing Astryx modal. The toast card is no longer a live region inside a viewport, including while a modal hosts it. (#7871)
  • Tokenizer forwards cancel to its searchSource, so a newer search, closing the menu or the sheet, focus leaving the field, or unmounting cancels the consumer's in-flight search (for example, to abort its request). Previously the inline field wrapped the source to filter selected items and dropped cancel, and the bottom-sheet presentation never called it. (#8777)
  • A Toolbar with centerContent wraps its row when its lanes don't fit, as at a larger text size on a phone, instead of letting the center title spill over the buttons beside it and past the screen's edge. The end lane, and the center lane when it does not fit beside the start lane, move to a following line. The center sits at the toolbar's middle as before while each side lane fits in half of the width it leaves. In a narrow container, a center TabList now shows all its tabs and the row wraps, and its tabs scroll only when they are wider than the toolbar. (#10563)
  • A controlled Tooltip held closed (isOpen={false}) no longer opens on keyboard focus or a click into a text-field trigger. It reports that focus as onOpenChange(true) and shows nothing, so the caller decides, the same way Escape on a held-open tooltip reports onOpenChange(false) without hiding. Before, focus opened a held-closed tooltip anyway, and Escape could not close it. useTooltip reports the same focus through onShow under isOpen={false}. (#10490)
  • on a touch screen, keys typed into a text field no longer make the focus a closing dialog returns to a Tooltip or HoverCard trigger open its layer; Tab, Escape and arrow keys still count as keyboard input. useTouchTrigger's isTouchInteraction() from @astryxdesign/core/Layer stays true in that case too. A field in an iframe or Picture-in-Picture window is not read as a text-entry field, so typing there still opens the tooltip as before. (#10639)
  • A disabled TopNavItem now keeps its Tab stop, in both the bar and the drawer. Before, it rendered with tabIndex={-1}, so Tab skipped it and keyboard and screen-reader users could not reach it. Now it is a focusable link that exposes aria-disabled="true", while a click, Enter or Space still runs no onClick or onKeyDown, does not navigate, and does not close the mobile drawer. No API changes. (#9208)
  • TopNav's heading can now shrink, so a heading wider than the whole bar ends in an ellipsis instead of running off the bar and scrolling the page sideways. TopNavHeading keeps its logo whole, and independently linked lines wrap and keep their longest word; a plain line beside them still keeps its full width. (#9551)
  • TopNav wraps its bar when its regions don't fit one row, as at a larger text size, instead of letting the end content (such as buttons) cover the navigation items. The end content moves to a second line. While the regions fit, the bar and its centered content look as before. (#10571)
  • DateInput's touch sheet keeps keyboard focus when the month reaches the end of the range, by an arrow press or a swipe, while a month arrow holds focus. That arrow hides there, so focus now moves first to the other month arrow, or to the month-and-year button when both arrows hide. Before, focus fell to the page. (#10231)
  • Toast: the useToast fallback warning and its server-rendering error no longer tell you to wrap the app in <AppShell>. AppShell provides no layer context, so that advice left the warning in place. They now name only <LayerProvider>, which removes it. (#10875)
  • With a mouse or trackpad, a date or time sheet's wheel no longer turns back to the row a key step is leaving. A key step commits its row at once and then scrolls there. On a busy page or a slow device the scroll could draw no frame for longer than the wheel's quiet period, or the browser could end it part-way, and the wheel took that pause for rest: it committed the row under the band and turned back there. A rest before the step's row is reached now finishes the scroll instead. A scroll a person makes still rests where it stops. (#10610)
Performance
  • Closing a Popover or DropdownMenu with Escape, or a DropdownMenu with a pick or a press on its trigger, runs one layout again, not two. A closed trigger stops being a CSS anchor, and these closes took the trigger's anchor name away after the hide's own layout, so the browser laid out once more. Our hide now drops the name before its layout, unless the layer's closed state keeps it shown to fade out. A close the browser runs itself, such as a light dismiss, still drops the name at its toggle event. A layer that fades out keeps the name until its fade ends. (#10346)
  • Popover, DropdownMenu and its submenus, Selector, ComplexSelector, PowerSearch and Breadcrumbs' menu play their entrance on the surface inside the layer, not on the anchored layer. Chromium laid the anchored layer out again on every frame of its 150 ms entrance, two to four times per frame, whenever the page had other frame work. The entrance looks the same. layerAnimations is unchanged; its docs now say to apply it to the surface. Applied to the layer, it still plays as before. (#10561)
  • While a Tooltip or another anchored layer plays its entrance, most reads of the layer's box write no styles. Before, each read during the entrance overrode the layer's transform, read the box and put the transform back, so the browser recomputed style and layout twice in that frame (measured in Chromium: 8 style writes, 2 style recalculations and 2 layouts per read). Now a read on the middle frames of an entrance takes the entrance transform out of one box read by calculation, and gets the same box. The read that shows the layer and any read while its entrance is pending, a read whose box does not yet carry the entrance (in Chromium, a layer at a fallback position), the last frames of an entrance, a layer under a CSS zoom other than 1, and a translate given as a percentage still use the override, as before. Placement, the entrance animation and the keyboard cap do not change. (#10240)
  • Motion: a Switch at rest holds no compositing layer under a coarse pointer. Its colour fade and its lift's shadow take a layer only while they move. (#10542)
  • Motion: the motions that one callback starts on elements that came in the same task read their stylesheets' will-change in one style pass, after the callback. Before, each element forced a style pass of its own: eight for a list whose eight rows glide together. (#10728)
  • Under a finger, Popover plays its growth on the surface inside the layer, not on the anchored layer. Chromium restyles the growth's animations twice as they start and once as they end, and each restyle laid the anchored layer out twice, its backdrop included. Under load those layouts landed inside the growth. The popover looks the same. (#10717)
  • Under snap paging, a Carousel's release bakes the settle's keyframes once, not once per item, and plays the settle only on the items that can show. With 9 items the release takes about a third less main-thread time, and with 30 items about two thirds less. (#10568)
  • useTableRowIndex builds its number column once per plugin, so a parent re-render no longer re-renders every row of a table that shows row numbers. (#10654)
  • Truncating Text and Heading take a newly mounted element's first measurement from the shared resize observer's first notification, after the browser's own layout, instead of forcing a layout pass after each commit. Pages and windowed tables that mount many truncating texts commit faster; the tooltip behaves as before. (#10668)
Documentation
  • The source header of Layout/containerCorners.stylex.ts (shipped in the package) now says that the --container-corner-* variables Card and Dialog set are in astryx.css, undocumented, and read only by Table and List; it had said they stay out of public API. (#10701)
  • Hook docs for useCalendarConstraints, so astryx hook useCalendarConstraints and astryx search return it, and a useCalendarConstraints — Hotel Booking Range example block: a booking range picker that enforces min/max dates, disables closed Mondays, and caps reservations at 7 nights once check-in is selected. Copy it with astryx template useCalendarConstraintsHookUsage <path>. (#10151)
  • Hook docs for useCalendarNavigation, so astryx hook useCalendarNavigation and astryx search return it, and a useCalendarNavigation — Month Pager example block: a month-by-month calendar with Previous/Next controls, localized month-year header, and cross-month arrow key navigation using pendingFocus. Copy it with astryx template useCalendarNavigationHookUsage <path>. (#10154)
  • Hook docs for useLinkify, so astryx hook useLinkify and astryx search return it, and a useLinkify — Links in a Comment Thread example block: plain-text comments where the URL and email become Links and a custom [#123](https://github.com/meta/astryx/pull/123) issue-reference pattern shows the patterns option, while a comment without matches stays plain. (#9969)
  • Add usePowerSearchConfig hook docs and a filtered directory table example block (#10660)
  • Add useTableColumnSettingsState hook docs and a column visibility picker example block (#10652)
  • HoverCard: a trigger inside SVG <foreignObject> cannot be a CSS anchor in Chromium, so its card opens at the viewport corner. The docs now say so and show the fix: render the trigger in an HTML layer positioned over the SVG node. (#10908)
  • LayoutPanel's JSDoc example wraps its Layout in a Card instead of LayoutContainer, a component Astryx does not have. (#10716)
  • ChatLayout's guidance explains how a reply gets one right edge: Markdown prose keeps its 680px measure while code blocks and tables span the message column, so pass contentWidth="100%" to the reply's Markdown. Markdown's default measure is unchanged. (#6608)
  • useClickableContainer documents a pressable surface without Card chrome: the hook on the surface, usePressFeedback with interactionOverlayStyles.backgroundColor for the hover tint and touch press, a visually hidden <button> or <a> as the named control, and focusOutlineStyles.focusWithin for the shared focus ring that ClickableCard draws. ClickableCard's docs point chrome-free use to it. (#10880)
  • The collapsible, collapsedSize, isCollapsed and onCollapseChange descriptions in the Resizable and useResizable docs name what collapses a region, a lift or a key step under the collapsed size rather than a drag alone, and what reports a collapse change. (#10635)
  • Section's docs show how to center it: set marginInlineStart and marginInlineEnd to 'auto' in xstyle. (#10207)
  • SegmentedControl: the label contrast guidance says the track is translucent, so label contrast depends on the background behind the control, and asks you to check the labels on every background it sits on, including a custom page color. (#10882)
  • SideNavCollapseButton's docs now list every key its collapsible prop takes: the whole controlled config SideNav gets, not only isCollapsed and onCollapsedChange. (#10282)
  • The Skeleton radius prop's description no longer says 4 is 16px. 4 maps to the same container radius as 3 (12px), so the two values draw the same corners. No behavior change. (#10750)
  • Tab's docs show how to give a tab help text: anchor a Tooltip on the Tab through its ref, so the description lands on the tab, and put a decorative info Icon in endContent. endContent is documented as non-interactive: a button, link, or InfoTip inside it would nest a control inside the tab's button. (#10734)
  • Tab's docs show how to run the selected indicator edge to edge in one strip: a nested Theme that takes the app's color mode, extends the app's theme and sets insetInline: '0' on the tab-indicator target, so other TabLists keep the default indicator. The override is best effort across releases. (#10814)
  • TableSelectionToolbar documents how to select every row that matches a query across server pages with today's API: the app keeps "every matching row minus exclusions" and passes the toolbar its own count and label. In this mode the toolbar's selectedKeys holds only the loaded rows. (#10271)
  • The Tailwind guide (astryx docs styling-libraries/tailwind) adds a recipe for an app that already uses Tailwind: keep the app's own @import "tailwindcss", put the @layer line above it, and add the Astryx stylesheets after it. It explains why the @layer line must come before the Tailwind import: below it, the Astryx reset outranks every utility class, and nothing reports it. The Core README's Next.js + Tailwind section points to it. (#10532)
Other Changes
  • Internal: a ChatComposerInput source comment that restated the code is removed. No change to behavior or output. (#10811)
  • Internal: Core's internal touch entry re-exports the action-group tracking hook, which gains a no-paint option and press callbacks for Lab's TabBar. A tab-bar string joins Core's message catalog. Apps import nothing new. (#9699)
  • Internal: the undocumented @astryxdesign/core/internal/reorder entry also gives Lab's ListInput List's reorder session for rows that are not ListItems: useListReorderScope and ListReorderScope. List runs its own rows' session through the same session hooks, so its callers see no change. A ListInput string joins Core's message catalog. Internal entries are outside the public API and its compatibility promise. (#8163)
  • Internal: the undocumented @astryxdesign/core/internal/reorder entry lets Lab's TransferList and TransferListSelector reorder through a createReorderable object: adaptReorderable runs the owner's engine with the collection's own moves, and the owner's start(key) still finds the collection's list. Existing List callers are unchanged. Internal entries are outside the public API and its compatibility promise. (#8143)
  • Internal: Core's internal touch entry re-exports its scroll test for Lab's TabBar. Apps import nothing new. (#10791)
  • Internal: per-instance warning deduplication and temporary focus targets each have one shared owner in Core. Resizable, Dialog and TabList dedupe their development warnings through it, and Chat's Done button parks focus through it. Warning text and focus behavior are unchanged; apps import nothing new. (#10655)
  • Internal: the More tab's label, a tab-bar string, joins Core's message catalog for Lab's TabBar. Apps import nothing new. (#10791)
  • Internal: Core's internal finger-scroll reader can answer for a past time on the page's clock, for Lab's NavigationStack scroll edge. Apps import nothing new. (#10540)
  • Internal: the undocumented @astryxdesign/core/internal/line-clamp entry gives Lab's LineClamp Core's focusable selector, the shared mutation observer and its flush, and the shared truncation tooltip. The shared mutation observer now passes each registration the records that reached it, and existing callers ignore them, so their behaviour is unchanged. Internal entries are outside the public API and its compatibility promise. (#4259)
  • Internal: the layer's outside-press watch can follow chosen pointer types, close as a press that starts outside begins to pan (on either axis, at core's pan threshold) or when the browser takes it, and judge a press inside a closed shadow root, which the document sees as its host. No component passes these options yet, so every watch keeps today's behavior. Not exported from the package entry point. (#9814)
  • Internal: Popover keeps its chosen presentation (the sheet or the anchored layer, the touch grow or the pointer entrance) from the open until its close settles through the layer runtime's one presentation hold (Layer/presentationHold.ts). No behavior change. (#8587)
  • Internal: one owner module now turns the browser's scroll anchoring off on a container whose position a component owns. useChatStreamScroll uses it while it follows the end, with the same behaviour as before, and the undocumented @astryxdesign/core/internal/scroll-anchoring entry gives its writer to Lab. Internal entries are outside the public API and its compatibility promise. (#10173)
  • Internal: Selector and MultiSelector keep the presentation an opening chose, and a closing sheet mounted until its focus handoff, through the layer runtime's presentation hold (Layer/presentationHold.ts). No behavior change. (#8591)
  • Internal: Core's shared-realm module gains helpers for state that the package and a swizzled copy share (state, maps, stores, brands and sequences). No API or behavior changes. (#10817)
  • Timer's tick pipeline, format ladder, cadence switch, and resource cleanup were audited with no behavior defect found. Two previously untested guards are now pinned: the wait for a distant future startTime is capped at the 32-bit setTimeout ceiling, and an unknown format value coerces to elapsed. The Default story now asserts in a real browser that the display advances on its own. (#6609)
Contributors
Thanks to everyone who contributed to this release:

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: