What's New

Release notes and changelog for all packages.

0.7.16

Experimental APIs
  • Adds the English strings of the Lab media player (@astryx.mediaPlayer.*): control names, spoken times, chapter and marker context, and previous and next track. They are Lab strings shipped in Core's locale file, as Lab ListInput's strings are; they add no public API to @astryxdesign/core. (#11438)
New Features
  • NumberInput takes entryErrorBehavior, so a form can pass one value to all of its date, time, and number fields. A typed number is complete only at Enter or blur, so both values keep NumberInput's current timing: its rejection, aria-invalid, announcement, and onEntryErrorChange report appear at Enter or blur, never while a person types. Setting the prop, or FormLayout's defaultEntryErrorBehavior, changes nothing a person sees in a NumberInput. Pagination's page box passes 'complete', so a FormLayout around it never changes it. (#11492)
  • DateInput, DateTimeInput, and TimeInput take entryErrorBehavior, and FormLayout takes defaultEntryErrorBehavior. The prop sets when a field shows its own entry error, such as a date the calendar does not have or a time outside min and max. It does not set when validation runs, and it is not React Aria's validationBehavior. 'complete', the default, keeps each field's current timing. 'blur-or-enter' holds the message, aria-invalid, the invalid styling, the announcement, and the onEntryErrorChange report until the person presses Enter or leaves the field; an edit that makes the entry valid or empty still clears the error at once. A field's own prop wins over the form default, a nested FormLayout replaces it, and a Dialog opened from the form starts without it. PowerSearch value editors and Table filter editors keep 'complete'. The new EntryErrorBehavior type names the two values. (#11485)
  • A Lightbox gallery's caption sits in a band two lines tall under every photo, so the photo keeps one size and place from item to item. A photo with no caption keeps the band's space without its backing. A longer caption shows two lines, the second ending in an inline "more" link, which opens the whole caption over the photo. The whole caption is always the viewer's accessible description. (#9810) The viewer is a media surface: its controls, caption and counter take the theme's dark surface tokens through MediaTheme. The caption is body Text whose lines start at one edge, "more" and "less" are Link's button form in the caption's own type, and the band clears the screen's bottom edge and its safe area. A gallery's caption sits on a backing that keeps it at 4.5:1 over any photo. A tap that opens the viewer paints no focus ring on its first control, and paging from a focused "more" or "less" keeps focus in the viewer.
  • NumberInput: onEntryErrorChange reports why the field rejects typed text, so an app can word its own message. It receives a NumberInputEntryError with a kind that does not depend on the locale (unreadable, fractional for a fraction when isIntegerOnly, or outOfRange for any number while min is above max), the typed text, and, for fractional and outOfRange, the number as value. It runs each time the rejection changes: at Enter or blur, when an edit makes the text valid or empty, when a new value, min, max, or isIntegerOnly changes or ends it, and when disabling the field drops the text. It reports null when the rejection ends, or when the field unmounts while one stands, and never twice for the same rejection. Pass an error status with a message to word the rejection; that message is the one announced. (#11415)
  • New message @astryx.richTextEditor.link.urlPlaceholder ("example.com"), the placeholder of the RichText toolbar's link field. The descriptions of the other @astryx.richTextEditor.link.* messages and @astryx.richTextEditor.toolbar.link now describe the link popover that replaces the link dialog; their messages are unchanged. (#8717)
  • Column windowing keeps focus and place: with useTableColumnsVirtualization, a focused cell whose column scrolls out of the window stays mounted with its original element until focus leaves the table, moves to another cell, or its column is removed, when focus returns to the Table's scroll area. Focus in a menu that a cell opens keeps the cell's column too. Changing column order, widths, visibility or pinning keeps the first visible column and how far it is scrolled. Tables that do not opt in are unchanged. (#11018)
  • Tables can window their columns: pass useTableColumnsVirtualization({initialViewportWidth}) to Table.virtualization. Table keeps every column definition and width, mounts only the unpinned columns near the inline viewport plus two overscan columns per side, keeps pinned columns mounted, and gives mounted cells full-table aria-colindex values with aria-colcount on the table. When the scroll area is at least as wide as the table's minimum width, every column mounts. Table.virtualization also accepts a list with at most one rows and one columns capability. Unsupported content or structure renders every column with a development warning. Adding or removing the columns capability remounts the table. Tables that do not opt in render as before; their Table import carries about 0.5 KB gzip of column windowing wiring, and the column planner loads only with the hook. (#11014)
  • Add Table infinite loading with useTableInfiniteScroll({hasMore, isLoading, onLoadMore}). One Promise request latch coordinates automatic and manual loading, failures pause automatic retry, and the persistent busy Button owns progress announcements and focus continuity. (#10570)
  • Tables can window rows and columns together: pass both useTableRowsVirtualization and useTableColumnsVirtualization to Table.virtualization as a list. Table mounts only the cells near the viewport on both axes, keeps full-table aria-rowindex and aria-colindex values, and keeps a focused cell's row and column mounted while either scrolls away. Tables that do not opt in are unchanged. (#11019)
  • TextArea htmlMaxLength sets the native maxlength attribute, so a form can cap typing in UTF-16 code units, including an SSR form before hydration. It is independent of maxLength, the soft counter, which still counts user-perceived characters and never blocks typing. TextArea adds no truncation or validation of its own, and renders no native maxlength when htmlMaxLength is unset. (#11295)
  • TimeInput: onEntryErrorChange reports why the field rejects typed text, so an app can word its own message. It receives a TimeInputEntryError with a kind that does not depend on the locale (unreadable, or outOfRange for a time before min or after max), the typed text, and, for outOfRange, the ISO time value. It runs each time the shown rejection changes, including when a new min, max, or value, or disabling the field, changes it, never twice for the same rejection, and with null when the rejection ends or the field unmounts while it stands. The native and bottom-sheet surfaces take no typed text, so they never report. (#11413)
  • useTruncation takes isExpanded: pass true while the text is shown in full; the hook keeps reporting whether it is cut off when clamped. A Lightbox caption uses it, so its "less" stays while the caption is open. (#9810)
Fixes
  • AppShell keeps server-rendered content when a screen is narrower than the server assumed. On a phone, the shell learned its mobile layout in an urgent update right after it hydrated. When the content inside the shell had not hydrated yet, because its code streams in or loads later, React rendered that content again in place of its server HTML: a visitor lost scroll position and focus, and images inside loaded twice. The shell now takes the client's breakpoint answer in a transition, which waits for that content to hydrate. A client-rendered app and a correct mobileNav.defaultIsMobile hint behave as before. No API changes. (#11441)
  • BottomSheet syncs its focus return target at commit, and no longer copies its stack view during render. A sheet removed after a render React discards, as a suspended transition does, returns focus to its committed finalFocusRef. (#10918)
  • BottomSheet: when a touch flick closes a sheet, the dim behind it now clears in step with the sheet. Before, the sheet was gone in about a tenth of a second while the dim was still mostly there, and it kept fading for over half a second more. The fade now follows the close spring's own progress. Reduced motion and every other close are unchanged. (#11400)
  • BottomSheet keeps its snap points and its reactivated entrance in state, and syncs its drag's stop resolver at commit. A render React discards that changes snapPoints, as a suspended transition can, no longer changes the stop a released drag rests at. (#10873)
  • ChatComposerInput: an empty input keeps its one-line height and takes typing after a page restyle, for example after an open Dialog that holds a SegmentedControl unmounts. Before, its editable area could collapse to 0px, so a click landed beside it and typing did nothing until a reload. (#11428)
  • useContainerReveal keeps revealed content always visible only when the primary pointer is coarse (a phone or tablet). A touchscreen laptop used with a mouse or trackpad now reveals on hover and keyboard focus like any other mouse device. Previously any touchscreen kept the content visible at rest, so a Thumbnail's hover remove button, Markdown heading links, and every app's hover-revealed row actions never hid. (#11218)
  • A theme's padding written with clamp(), calc(), min(), max() or var() with a fallback now builds as written. The theme compiler splits padding, paddingBlock and paddingInline on the spaces between values only, never on a space inside parentheses or quotes, so padding: clamp(8px, 2vw, 16px) stays one value instead of becoming broken CSS. No API changes. (#11347)
  • DateInput, DateTimeInput: a value that the app passes at an Enter or blur that keeps a rejected date no longer erases it, so the entry meets WCAG 2.2 3.3.1 (Error Identification). Before, when an app set value in the same update as an Enter or blur that kept unreadable, incomplete, nonexistent, or out-of-range date text, as an app does when it restores the date it had before the edit, the field dropped the text, its message, and aria-invalid, and reported null through onEntryErrorChange; a native date control lost its rejection message the same way. Now the text, its rejection, and its message stay at every such Enter or blur, a blur after an Enter included, so the person can correct the entry, and nothing is reported. A later new value replaces the text, as before. No app code changes are needed. (#11470)
  • DateInput, DateTimeInput: in a standalone field, rejected dates now meet WCAG 2.2 1.4.1 (Use of Color) and 3.3.1 (Error Identification); inside an InputGroup they set aria-invalid and are announced. Before, text that is not a date was marked invalid and announced on every keystroke, with no visible message, and Enter or blur reverted it. A native date control flagged each partial year while the year was typed, showed no message, and dropped the rejection when it restored the committed date at blur. Now text that is not a date shows nothing while you type; Enter or blur keeps it in the field and shows "Invalid date" as the field's error status, with aria-invalid and one announcement. Its message replaces a caller status, as the field's other rejections already do; with onEntryErrorChange, a caller error status with a message still wins. A native date control's rejection waits for Enter or blur, shows the out-of-range message a typed date shows, under the same status rules, and stays shown after the control restores the committed date at blur. A shown rejection stays through an edit that leaves the date wrong or unfinished, and clears once the date is valid or empty. What a form posts does not change: while kept text is not a date, a hidden input posts the committed date under the field's name, and the next Enter submits the form. (#11407)
  • SideNav, TopNav, Breadcrumbs: a Ctrl-, Cmd-, Shift- or Alt-click on a link in the mobile navigation drawer opens it the way the browser decides, a new tab for instance, and leaves the drawer open. A plain click still closes it, and so does a modified click that the row's own onClick cancels, since nothing opens elsewhere. (#8979) (#9390)
  • DropdownMenu syncs the refs its show and hide call at commit. After a render React discards, as a suspended transition does, its entrance under a finger holds input as the committed menu says. (#10905)
  • In forced-colors mode (Windows contrast themes), primary and secondary Buttons gain a ButtonText border, and destructive keeps its CanvasText border; in a connected ButtonGroup the solid buttons keep the group's dividers and close the group's outer edge, with no doubled seam. Floating surfaces that separate from the page with a box shadow alone gain a CanvasText border: Popover and every surface usePopover paints (including DropdownMenu), DropdownMenuSubMenu flyouts, ContextMenu, and an isInline Dialog. Forced colors removes fills and box shadows, which left these controls and surfaces without an edge. The borders exist only in forced colors, so nothing changes elsewhere. A theme that sets a solid variant's own border width keeps it, so Gothic's secondary Button stays borderless. (#7677)
  • A layer with several triggers now opens at another trigger when the press on that trigger is the one that closes it, with a mouse or a finger. A press on the open trigger still closes it. (#11337)
  • An anchored layer flush against its trigger, or over its edge, no longer slides over it: its entrance scales in place, as it does for a layer over its trigger's center. A menu at the pointer still slides from the side it lands on. (#11417)
  • An anchored layer that has room to its trigger no longer starts its entrance over it: its first step toward the trigger stops at that room. So a tall tooltip 4 px beside its trigger no longer covers it on its first frame in Safari. (#11396)
  • The layer runtime syncs its close-start and replayed-show refs at commit, not during render, and its keep-open press reads the committed open state or the shown layer. A render React discards no longer leaves its values for later callbacks. (#10912)
  • A light-dismiss layer opened while a press is released no longer closes at that release. A DropdownMenu or ContextMenu row that opens a Popover when chosen with a mouse now leaves it open, as it already did with a finger; the next press outside, or Escape, closes it as before. (#11258)
  • A mouse click on the dark space beside a Lightbox photo now closes the viewer. Before, the viewer stayed open after a click there within the photo's natural width, or within a wider caption's width. (#11354)
  • A single photo's caption in a Lightbox now shows as a gallery's does. It sits in the band at the bottom of the viewer, on the caption's backing, which keeps 4.5:1 over any page behind it. The photo centres above it. A caption longer than two lines ends in "more", which opens it in full over the photo. A single photo with no caption shows no band. (#10284)
  • When a reorderable List row does not render again, its handle's name still follows it. A handle named after its place ("Reorder item N") follows that place when rows above it go or the rows reorder. A label that gains or loses its text renames the handle. (#10815)
  • DropdownMenu, ContextMenu, Selector, TabList, TopNav, SideNav, Breadcrumbs: when a finger picks a menu row, the click guard cancels only that finger's touchend once the menu has named the touch, so another finger's touchend passes. The menu names the touch from the touchstart that follows its pointerdown. A touchend without changedTouches, or a lift whose touch the menu could not name, keeps the old rule: the next touchend is cancelled. (#11164)
  • MoreMenu, InfoTip, PowerSearch (with its PowerSearchToken and PowerSearchFilterEditor defaults), Toast, and InputClearButton now pass host data-* attributes to their own element, as other components do: the trigger button for MoreMenu and InfoTip, the primary control for PowerSearch, the token and editor root for the PowerSearch defaults, the toast element for Toast, and the button for InputClearButton. Component-owned attributes stay with the component. A new test renders every exported component that renders an element of its own with a data-* attribute, and fails when the attribute does not reach the DOM. (#11406)
  • NumberInput: a rejected entry now shows a message and stays in the field, so the field meets WCAG 2.2 1.4.1 (Use of Color) and 3.3.1 (Error Identification). Before, every draft that was not an accepted number, an unfinished one such as - included, set aria-invalid and was announced on each keystroke, while the text only turned secondary; blur then reverted a draft that did not parse, with no message. Now nothing is marked or announced while a person types, because a typed number is complete only at Enter or blur. At Enter or blur, text that is not a number, a fraction when isIntegerOnly, or any number while min is above max stays in the field: the field shows "Invalid number" as its error status, tied to the input by aria-describedby, sets aria-invalid, and announces it once. Inside an InputGroup the rejection sets aria-invalid and is announced. An edit that makes the draft valid or empty clears it at once. A number outside an ordinary range still clamps and commits through onChange. A caller error status with a message still shows in place of the field's message; a warning or success status no longer hides a rejection. What a form posts does not change: while blur keeps a rejected draft, a hidden input posts the committed number as the field showed it before. Pagination's input variant shows the message on its page box's status icon and widens the box beside the typed text while a rejected entry stays, so the bar keeps its height. No app code changes are needed. (#11415)
  • Under a finger, a Popover that overlaps its trigger now grows from where it meets the trigger, as the pointer entrance does. A popover a few pixels over its trigger's side grows from that side, not from below. A popover over its trigger's center grows from that center by scale only. Every other landing grows as before. (#10949)
  • Toast announces the rendered message when a body's text comes only from a component, and from custom layouts (#7853) (#11175)
  • SegmentedControl: where the control has no layout, as in a unit test's DOM, a click on a later segment keeps that segment selected instead of switching to the first segment a moment later. Browsers are unaffected. (#11487)
  • Selector's presentation syncs its show, hide and popover-content refs at commit. After a render React discards, as a suspended transition does, opening the popover runs the committed show. (#10917)
  • Slider syncs its values, change-end callback and touch update refs at commit. After a render React discards, as a suspended transition does, a press on the track reports the committed value to the committed onChangeEnd, and a finger dragging a thumb reports to the committed onChange. (#10913)
  • Table: useTableSortableState calls the onSortChange of the last committed render. Before, a sort click during a transition that had not committed yet called the callback from that pending render. (#11433)
  • TimeInput, DateTimeInput: a rejected typed time now meets WCAG 2.2 1.4.1 (Use of Color) and 3.3.1 (Error Identification). Before, every draft that was not an accepted time, an unfinished one such as 1 included, was marked invalid and announced on each keystroke, shown only as secondary-color text, and blur reverted it with no message; a native time edit outside min or max showed no message and its rejection cleared at blur. Now an unfinished time is never flagged: a time outside min or max shows once it is complete (its hours, both minute digits, both second digits when the field shows seconds, and in 12-hour text its day period unless the hour reads 0 or 13–23), and text that is not a time shows at Enter or blur. The rejected text stays in the field, and a standalone field shows the "Invalid time" message as its error status, with aria-invalid and one announcement; inside an InputGroup the rejection sets aria-invalid and is announced. Enter in TimeInput and in DateTimeInput's time field commits the typed time and still submits a surrounding form; in DateTimeInput's open preset-time list, Enter picks a time as before. A native time control restores the committed time at blur and keeps its rejection shown. A caller error status with a message still shows over the field's message, and the rejection is announced once; a warning or success status no longer hides a rejection. In DateTimeInput, a date rejection's message comes first and a time rejection under it is announced. What a form posts does not change: while blur keeps a rejected TimeInput draft, a hidden input carries the field's name with the committed time. (#11413)
  • TimeInput and DateTimeInput: a bound with no whole minute inside the range keeps its own seconds, so the clamp stays inside the range. Before, clampTime('12:00','23:59:30') answered 23:59 — below the minimum the caller set. In a TimeInput sheet a wheel rest past such a bound committed nothing; in a DateTimeInput sheet, changing the date onto such a bound committed the out-of-range 23:59. (#10159) (#10159)
  • Tooltip's and HoverCard's touch trigger, and Tooltip's handlers with the controlled and enabled flags they carry, sync at commit. After a render React discards, as a suspended transition does, a tap answers with the committed props, and a press outside still closes a shown tooltip. (#10892)
Performance
  • Markdown text transforms that declare requiredSubstrings look for those substrings in one pass over the source. Before, each paragraph searched the rest of the document again, so long Markdown (such as a long streamed chat answer) rendered more slowly with each paragraph. Output is unchanged. (#11403)
Documentation
  • The docs playgrounds for TextInput, TextArea, NumberInput, CheckboxInput, Switch, ProgressBar and StatusDot open with realistic values instead of prop-name placeholders, the Heading playground opens as a level-1 heading instead of inheriting Text's sample with type: 'body', and the ButtonGroup, TabList, SegmentedControl and TopNav playgrounds open with named sample items instead of numbered ones. (#11351)
  • Hook docs for useOutlineFromDOM, so astryx hook useOutlineFromDOM and astryx search return it, and a useOutlineFromDOM — Article example block: an article and an Outline built from its headings through the hook, with a button that adds a section and its linked entry. (#11234)
  • ListItem's startContent and endContent docs now say that the content sits inside the row, before the label or after the label and description, not before or after the item. (#11336)
  • MetadataList's guidance now says that assistive technology reads each label with its value, and that the title does not name the list or add a heading. Its prop docs now list className and style, and the label docs say that position: 'start' places a label at the inline start of its value, not on the left. (#11391)
Contributors
Thanks to everyone who contributed to this release:

0.7.15

New Features
  • DateInput, DateTimeInput: onEntryErrorChange reports why the field rejects typed text, so an app can word its own message. It receives a DateInputEntryError (exported from both components) with a kind that does not depend on the locale (unreadable, incomplete, nonexistent, outOfRange for a date before min or after max, or unavailable for a day that dateConstraints rules out), the typed text, and, for outOfRange and unavailable, the Gregorian ISO date. It runs each time the rejection changes, including when a new min, max, dateConstraints, or value, a calendar pick, disabling the field, or Enter or blur changes it, and with null when the rejection ends, or when the typed field leaves while its rejection stands, as when a presentation or pointer change shows the native or touch picker. With the callback, an error status that has a message is the message the field shows and announces, and the field's own message applies only without one; a warning or success status never replaces a rejection. When a rejection starts while that error message stays the same, the field announces the message once more for it. Without the callback, nothing else changes. For every DateTimeInput, while a native date control replaces the typed date field, kept typed text and its rejection wait for the typed field, so the field shows the caller's status meanwhile. The native and touch pickers take no typed text, so the callback never reports a rejection there. Fixes #10366. (#11311)
  • SegmentedControl: under a finger, pressing the selected segment lifts its surface as UIKit's does, and it settles back when the finger lets go. A pen lifts it the same way on a touch device. With a mouse on a desktop, or with Reduce Motion, nothing lifts. (#9724)
  • Where the primary pointer is fine, a mouse press on a CheckboxInput or a RadioList option paints at once on pointerdown and fades on release, as a finger's press does, instead of the browser's :active. A right click, or a press on a link or a button inside a RadioList option, does not paint the option. Other controls keep :active for a mouse. (#8696)
Fixes
  • Calendar, DateRangeInput: a two-month calendar whose max falls in the month it would open on now opens with that month in the second pane. Before, with max set to today, or with a selected value starting in max's month, it opened on that month and the next one, and every day of the next month was disabled while the previous month stayed hidden. The first pane still never goes before min's month, an explicit focusDate is shown as given, and a one-month calendar is unchanged. (#11202)
  • Calendar: with hasWeekNumbers, each row shows the ISO 8601 week number of its Thursday, the ISO week that holds most of its days. Before, most rows that start on Sunday or Saturday showed the previous ISO week, so the first two rows of a month could show the same number. Rows that start on Monday are unchanged. (#11271)
  • DateInput, DateTimeInput: a typed date that the calendar does not have, such as February 30, shows "Enter a real date". The message names the calendar, as in "Enter a real date (Persian Calendar)", only when the field's calendar differs from the InternationalizationProvider calendar. A day that dateConstraints rules out shows "Enter an available date". (#11309)
  • DateInput keeps its typed field's and native field's bookkeeping in state. A render React discards, as a suspended transition does, no longer drops typed text, clears a refused date, or reports the same date twice. (#10877)
  • DateTimeInput keeps its native pickers' last value and commit epoch in state. A render React discards, as a suspended transition does, no longer drops a time chosen before the date, clears a refused date or time, or lets the same native edit commit twice. (#10861)
  • Drawer keeps the side it exits to in state. A render React discards, as a suspended transition does, no longer changes the edge a closing drawer slides out to. (#10859)
  • useLinkify and RichTextEditorAutoLinkPlugin: email detection now takes linear time. A long word with no email in it, such as a pasted hash or base64 string, no longer freezes the page for seconds. Valid email addresses link as before, with three exceptions. In the rich-text editor, an address directly after a period no longer links, and a quoted local part ends at the next quote. In useLinkify, a fragment glued to the end of an earlier address no longer links on its own. (#11306)
  • Dialog, CommandPalette, BottomSheet, Lightbox, Drawer, MobileNav, Popover: a Tab pressed with Ctrl or Meta on the first or last control of a modal no longer moves focus to the other end, and the modal no longer cancels the press. A page or a host app that handles Ctrl+Tab or Meta+Tab itself, for example to switch its own tabs, now gets the press on every control, as it already did between the first and the last. Alt+Tab still wraps, because Safari moves focus to each item on Option+Tab. (#11247)
  • Gestures in a same-origin iframe or a Picture-in-Picture window now time touches on that window's own clock. Before, a short tap there could start a long press, because the page's clock reads ahead of the window's. (#11155)
  • Item's swipe actions: under reveal, a fling opens the row at its actions; under either model a fling never fires an entry. On a side with two or more entries, only a drag that starts on the open row fires the outermost entry. The panel shows no entry's colour behind another. The entries fill it, and the entry that fires covers it until the row comes back or holds out. No API changes. (#11054)
  • Keep disabled Item actions focusable (#11169)
  • After the window loses focus during a finger's press, lifting that finger no longer acts on any menu (DropdownMenu, MoreMenu, ContextMenu, Selector, and menus built on the public useMenuPress), and a tap on a menu's trigger still opens it. Under a finger, a row lit by a press that is cancelled (a scroll, a second finger, the window losing focus) now clears, as on iOS. It clears in DropdownMenu and its sub-menus under any presentation, MoreMenu, ContextMenu, Selector's list and the bottom sheet's action list, and in a menu built on the public useMenuPress whose root can take focus. A mouse keeps its highlight. (#8508)
  • The menu press model behind DropdownMenu, ContextMenu and their submenus syncs its option, step and trigger-context refs at commit. A press after a render React discards, as a suspended transition does, now uses the committed options. (#10901)
  • The mobile keyboard hook syncs its enabled, expanded and open flags at commit. After a render React discards, as a suspended transition does, a dismissal and the keyboard's listeners follow the committed options. (#10914)
  • Outline's scroll spy reads its items, its onActiveIdChange and its active item as committed. A render React discards, as a suspended transition does, no longer changes which item a scroll marks or which callback a landed navigation calls. (#10802)
  • Carousel paging: a row that resizes while it settles no longer stops at once or runs back to an earlier page. The settle plays on at its speed, to the last page when it was heading there, and otherwise to the page nearest where it was heading. It ends on that page with no step when it goes back to native scrolling. A resize that leaves the row past its new last page, or that gives the row its first width, still lands it at once on the page it was heading for. (#10592)
  • ResizeHandle reads its region, direction and disabled state as committed. A render React discards, as a suspended transition does, no longer makes a key press resize another region or refuse an enabled handle. (#10803)
  • In a swizzled AppShell, the first Tab into the main region now stops on the region, as in the package's AppShell, when its first link or button sits inside a package scroll region that does not overflow (ScrollableArea, Table, CodeBlock, Tokenizer, BottomSheet), and the reverse. Arrow and Page keys are unchanged. No API changes. (#11225)
  • A disabled Step now reflects disabled on the step-indicator theming target, beside step-label, so a theme can restyle a disabled step's indicator. In a compact horizontal Stepper with on-track indicators, where a disabled step's label is not shown, the indicator is the only target a theme can reach. The step and step-description targets do not gain the selector. (#8997) (#9192)
  • useStreamingText keeps where its reveal restarts in state. A render React discards, as a suspended transition does, no longer restarts a streaming reveal from the start or jumps it to the end. (#10862)
  • Table keeps one array for each list of columns, and for each list of plugins, compared by identity. A render React throws away, as a suspended transition does, can no longer replace the array the table last displayed. The next committed render reuses the array, so rows skip rendering when the columns and plugins match the committed ones. useBaseTablePlugins also keeps its array when the base plugins come in a new array of the same plugins. A column plugin with its own render-time cache, such as the tree plugin, still re-renders every row. (#10940)
  • useTableSortableState sorts only when its data, sort or locale changes. It re-sorted every row on every render of its owner. (#10942)
  • Table sorting with useTableSortableState calls the latest onSortChange. Before, a sort header kept the handler from the last time the sort changed, so a parent that passed a new handler without a sort change had its old handler called, and that handler saw out-of-date state. (#11349)
  • Text and Heading: on Android, the first tap on a button or link inside truncated text opens the truncation tooltip, as on iOS. The tap focused the element first, and that focus took the tap; now only a keyboard focus counts. Tooltip: a tap on a text field inside a tooltip's trigger focuses the field and no longer opens or closes the tooltip. This includes a text field inside truncated text. (#11213)
  • A Timestamp hover card's copy button now shows when the clipboard write fails, as CodeBlock's copy button does: the icon becomes a cross for 1.5 seconds, and the button is named, tooltipped and announces "Failed to copy value to clipboard." It used to do nothing. A theme that maps the timestamp-copy slot keeps its rest glyph during a failure (copied is false). The error itself is not shown. (#10434)
  • ToastViewport syncs its committed list at commit. A toast that only a render React discards showed, such as a suspended transition, reports no onHide when a repeat replaces it and the same handler then dismisses it. (#10902)
  • Tokenizer's sheet numbers its searches and its opens in state. A render React discards, as a suspended transition does, no longer makes a reopen announce a search that never ran. (#10886)
  • In Tokenizer's inline field on a touch screen (a tablet, or presentation="popover" on a phone), removing a token with a finger no longer raises the touch keyboard. A tap on a token's own remove button (Token's ×) used to move focus to the field's input inside the tap, which makes iOS and Android show their keyboard; when the input was not focused before the tap (the keyboard was down), focus now stays where it was, unless the tapped × or another control in its token held focus, when focus moves to the input as before. A tap made while typing, a pen's tap, a mouse click, a key press on the remove button, and a remove control drawn by a custom renderToken still put focus in the input. PowerSearch's filter tokens, which render Token, get the same fix. (#8160)
Documentation
  • Hook docs for useThemeName, so astryx hook useThemeName and astryx search return it, and a useThemeName — Active theme example block: the name of the theme wrapped around the caller. (#11235)
  • List's anatomy now names its optional header and drops a description part that List does not render. The ref docs now say that the ref reaches the list element, with or without a header. (#11277)
  • DefinedTheme.__componentIcons is now documented public API; its presence and shape follow the compatibility policy. (#11192)
Other Changes
  • Internal: Core's internal touch entry re-exports UIKit's timing table and the motion engine's AnimateOptions and MotionHandle types for Lab's SearchField. Apps import nothing new. (#10956)
  • Internal: the close button name of Lab's SearchField joins Core's message catalog. Apps import nothing new. (#10956)
  • Internal: Core adds two internal hooks that keep a ref at the latest committed prop or callback for event and gesture callbacks, and an internal entry through which Lab reaches them. Outline's scroll spy, ResizeHandle and resizing logic, menu press handling, the mobile keyboard hook, and ToastViewport use them. Apps import nothing new. (#11352)
  • Internal: one shared context request from a long press, a right click, or Shift+F10 and the context-menu key, reporting which input made it, one per gesture. A held finger's hold loses to a claim another gesture already made on that finger, and a control that keeps its press for a hold-repeat owns only its hold, so its right click and Shift+F10 still reach the request. A held pen's own context menu event is refused like a held finger's. The hold is UIKit's long press and requests as it begins. Not exported from the package entry point. (#8670)
  • Internal: Core's internal layer hook drops a dismissal-check field that no component reads. The layer still refuses to reopen during the press that closed it. Apps see no change. (#11332)
  • Internal: Markdown records its streaming fade-in refs as an exception to the runtime's ref rule, with tests that pin why it is harmless. (#10939)
  • Internal: the rule that ends a container's press for a press on a nested control is named for every pointer it covers, and its comments and records say what it does. No change to any component's behavior or API. (#11304)
Contributors
Thanks to everyone who contributed to this release:

0.7.14

New Features
  • ComplexSelector: disabledMessage explains why a disabled selector is disabled. With isDisabled, a tooltip shows the reason on hover and keyboard focus, and the reason describes the trigger through aria-describedby. The disabled trigger keeps its tab stop, and pointer, keyboard and the imperative handle still cannot open the popup. With renderTrigger, the caller owns the control, and disabledMessage works with it too: the tooltip and the description go to that control. Drop the control's own tooltip while the selector is disabled, for example tooltip={isDisabled ? undefined : 'Filter'}, so it never shows two. Separately, a caller's own aria-disabled now reaches an enabled built-in trigger. (#5984)
  • An anchored layer's entrance now slides from, and scales about, the side the layer lands on. Before, a layer that flipped because its requested side had no room still slid from that requested side, onto its trigger. The entrance also scales about the point where the layer meets its trigger, not the center of its box. A Selector list that opens over its selected item scales about the trigger's center and does not slide. This applies to Popover, DropdownMenu and its submenus, ContextMenu, Selector, ComplexSelector, Tooltip, HoverCard, Breadcrumbs and PowerSearch menus, and any layer that uses the shared entrance. Built-in layers have no option that keeps the old entrance. The public layerAnimations styles now also set transform-origin; a caller's own transformOrigin listed after them still wins. (#10771)
  • useMenuPress with no longPressDelayMs now follows DropdownMenu's finger rules on every device: a finger or a pen opens the menu as it presses (inside a scroll view, once the 150 ms content-touch delay has passed), and the finger that opened it picks a row only after moving 10 px. To keep the previous behavior, a 500 ms hold and a pick at the opening finger's lift, pass longPressDelayMs: 500. (#8078)
  • Under a finger or a pen, on every device, the trigger of an anchored DropdownMenu or MoreMenu now opens its menu as it is pressed, instead of after a 500 ms hold. Inside a scroll view it opens once the 150 ms content-touch delay has passed with no scroll, so a scroll that starts on it still scrolls. To keep the previous behavior, a tap that opens at the lift and a 500 ms hold, pass presentation="popover". A menu shown as a bottom sheet, and a mouse, are unchanged. (#8078)
  • SegmentedControl: a drag that drifts off the control keeps choosing by its horizontal position, clamped to the end segments, and the lift commits that segment. A mouse or a pen drags the same way. Escape or a browser cancel takes the press back, and the highlight returns at once. (#10978)
  • Tokenizer is now an InputGroup-compatible control (#3520). Inside an InputGroup it consumes InputGroupContext instead of rendering its own Field, so the group owns the single label, description, and status chrome — no more duplicated label or nested field wrapper. The typeahead input is named by the group label plus the Tokenizer's own label (composed with getInputARIA, so aria-describedby merges the group's description/status with the input-local disabled reason rather than replacing it), and the control adopts the shared groupStyles.inGroup border/radius treatment so it joins the group's seam. The group also owns size, the disabled state, and validation: a disabled group disables its Tokenizer, a grouped Tokenizer takes the group's size (an explicit larger size no longer escapes the row), and its local description/status are neither referenced from aria-describedby nor painted beside the group's status. Because the group is a fixed-height single-line surface, a grouped Tokenizer keeps its tokens on one scrolling row instead of wrapping past the shared border — cap selections with maxEntries or summarize them with tokenOverflowBehavior. Its end controls (the clear button, endContent, and the busy indicator) hold the end of that row: tokens scroll beside them, never underneath. The row hides its native scrollbar and fades whichever edge hides tokens instead; forced colors bring back a thin native scrollbar. Keyboard users reach hidden tokens through their remove buttons (Shift+Tab from the input), and a disabled Tokenizer's row becomes its own Tab stop while it overflows, named by the Tokenizer's label, so the arrow keys can scroll it. (#4405)
  • TimeInput, DateTimeInput: under a finger, the bottom sheet's minute wheel loops, as UIDatePicker's does: past 59 comes 00, and the hour stays, as on iOS. A drag, a fling, a tap or an arrow key passes the seam. Home, End and a click on a minute never pass it. The hour wheel does not loop yet. Each minute is still listed once for assistive technology. (#10953)
Fixes
  • When a page mounts both the package's AppShell and a swizzled AppShell as outermost shells, only the first now keeps the fixed main-region id; the other takes a generated id, as two package shells already did. Before, each copy kept its own claim list, so both shells used astryx-app-shell-main and the page had a duplicate id. No API changes. (#11208)
  • BottomSheet: a finger's pull down on the sheet's content is handled by the sheet's touch listeners alone, and it releases at the speed of the whole pull. Before, the content's pointer handlers, which serve a mouse or a pen, began the same drag first and took pointer capture, and the capture change cancelled that drag one move later. The touch listeners then began the drag again, or, in Chromium, the content's own pan could start under it. The release speed counted only the moves after the drag began, so a fast flick on the content that the page received as two or three moves read as no speed and sprang back, where the same flick on the grab handle closed the sheet. A flick on the content now closes the sheet as a flick on the grab handle does. This also applies to the sheets that Tokenizer and PowerSearch open. A mouse or pen pull from the content also releases at the speed of the whole pull. No release threshold changes. (#11145)
  • BottomSheet: a move of a touch drag no longer restyles the sheet's content. Each move writes the scrim's opacity on the dialog as a custom property, and the property inherited into the sheet, so the browser restyled every element in the sheet on every move: 51 elements a move in a Tall sheet with a short list, 84 in PowerSearch's Filters sheet with three filters, and more with more content. The sheet's panel now ends that inheritance, and a move restyles the dialog, its backdrop, the panel and the edge tint. The scrim follows the drag as before. This applies to the sheet that owns the scrim: a single BottomSheet, or the first sheet of a stack, such as PowerSearch's Filters sheet and Tokenizer's sheet. (#11154)
  • BottomSheet: in Safari, and in every browser on iPhone and iPad, a swipe on the sheet's content that starts slowly now moves the sheet, so a slow swipe down can close it. Before, on content that fits, when the finger's first move was 8 px or less, in either direction, the sheet stopped answering that swipe: it stayed open, or moved a few pixels and fell back. Fast swipes and swipes on the grab bar already worked, and Chromium browsers were not affected. The fix applies wherever the touched content has nothing to scroll: a sheet whose content fits, and the fixed header or footer around a list. That includes the PowerSearch and Tokenizer sheets. At the top of a list that scrolls, a pull down now also moves the sheet when the finger first wobbles up by less than 5 px; a move up of 5 px or more still scrolls the list. In every browser, the sheet now decides who owns a touch on its content once, at the first move past 8 px. A mostly vertical pull at a scroll edge is the sheet's. A mostly sideways move, such as a swipe along a row of chips, is not the sheet's for the rest of that touch. Before, at the top of a list, a sideways swipe that drifted more than 8 px down, or a pull that began more sideways than down, also moved the sheet. (#11140)
  • Button: a disabled or loading submit or reset Button, including one in a disabled ButtonGroup or InputGroup, no longer submits or resets its form when clicked in server-rendered HTML before the page hydrates or when JavaScript fails to load. It renders as a plain button until hydration, then takes its own type again, with no change to what people see or hear. (#11107)
  • A Carousel's scroll buttons no longer cover the scroller's keyboard focus ring. Each button now sits just inside the ring instead of straddling the carousel's edge, so the whole ring stays visible while the scroller has focus (#10722). (#10726)
  • A transient copy that carries an animation still waiting for its first frame now runs it in step with the original. On a busy page, the SideNav rail's leaving copy could start the toggle's press fade a frame or more after the toggle's own. (#10983)
  • CommandPalette: refresh results when its searchSource changes while it is open. (#9679)
  • createISOTimeString answers null unless the trimmed string is H:M or H:M:S with one or two digits per field (a seconds fraction is still accepted and dropped), instead of reading "2:30 PM" as 02:30 (12 hours off) and "14:30abc" as 14:30 (#11023)
  • FileInput's dropzone shows its status message below the drop area by default, so it no longer covers the drop area; an explicit statusVariant="attached" still renders as before. (#11195)
  • A pan over the page that the browser doesn't take as a scroll no longer closes an open popover or selector list, and no longer taps the page element under the finger. (#11038)
  • A swizzled overlay and the package's components now share one set of focus regions and one mobile keyboard model: nested focus regions from the package and a copy no longer both answer the same Tab, and package and copied fields agree on the keyboard's height, its layout guide and which elements ride it. No API changes. (#10831)
  • On a phone, a press on a control at rest no longer measures the page, so a scroll that starts there does not wait. Hit areas no longer measure while the page scrolls or while a parent's animation moves them, such as a screen that slides in. A press on a control that a parent moves still measures the page. When a parent starts to move after the last measurement, the browser's own hit test decides the tap. No API changes. (#11083)
  • The arrow-key hint that Toolbar, TabList and SegmentedControl show on first keyboard focus now stays until you press an arrow key or Escape, or move focus out of the group (WCAG 2.2 SC 1.4.13 Content on Hover or Focus). It used to disappear after 3 seconds, sometimes before it could be read, and Escape did not close it. Escape now closes only the hint, through the shared layer dismissal stack, and keeps focus where it is. useKeyboardHint's dismissAfterMs no longer defaults to 3000; leave it unset. (#10564)
  • Closing a Lightbox stops a video that was playing. The viewer stays mounted, so the picture and its sound would otherwise continue after Close, Escape, or a tap outside. A viewer that is already closed does not start playback either. Opening it again plays the current video when hasAutoPlay is set. A video inside the caption stays stopped. (#10692)
  • A swizzled ListItem inside the package's List (or a package ListItem inside a swizzled List) now leaves the way a package row does: it keeps what it showed on screen, such as a swipe's travel, for its exit. Before, the List and the ListItem kept separate records of the rows the List reported and of the presentation a leaving row kept, so the row's exit lost that presentation. No API changes. (#11214)
  • Make onClick-only TopNav items keyboard accessible (#9334) Previously, onClick-only TopNav actions could be skipped by Tab or could not be activated from the keyboard. TopNavItem now provides button semantics and Enter/Space activation while preserving its anchor ref/event types and custom link rendering. Desktop TopNavMegaMenuItem actions and drawer TopNavMenu actions now use non-submitting native buttons.
    This restores keyboard operation and action semantics for WCAG 2.2 A criteria 2.1.1 and 4.1.2. Disabled TopNavItem actions remain focusable but cannot activate; href navigation and the existing desktop menu keyboard model are unchanged.
  • A fence plugin made with the package's createMarkdownFenceTransform now renders its node in a swizzled Markdown, and the reverse. Before, the copy described the plugin to its transform under its own keys, so the package's fence transform refused to run and the fence fell back to a plain code block. No new props, exports or defaults. (#11167)
  • Under right-to-left, plain text in InputGroupText, a Badge label and a Token label keeps the character order it was written in. Text with no right-to-left letter, such as a URL scheme (https://), a domain suffix (.com), a count (+3), C++, a handle (@alice) or a tag (#design), used to show reordered (//:https, com., 3+); it now lays out left to right. Text that contains a right-to-left letter keeps the page's direction, isolated from its neighbours, so iPhone جديد still reads right to left. A rich (non-string) label or child is isolated but keeps the page's direction: mark mixed directions on your own content. Plain InputGroupText text with no right-to-left letter sits in an inner span. Left-to-right pages are unchanged. (#10114)
  • A swizzled component that carries its own copy of Core's layout motion, spinner rotor or gesture sync now shares the package's: a layout change in one copy starts at the frame the other copy's change started in, so their glides land together; spinners from both copies are pinned to the timeline in one batch, so rings mounted together cost one style recalculation instead of one per copy; and a gesture sync running in one copy holds the other copy's gesture callbacks too. No API changes. (#11027)
  • Popover: initial focus takes the first content control in document order everywhere. This changes the focused control only where querySelectorAll does not return document order, as in jsdom; browsers focus the same control as before. (#11177)
  • Icons registered with registerIcons() now reach swizzled Icon, CodeBlock, Table and Timestamp copies on the same React. Themes registered by name are now shared by every Core bundle loaded on one React. Each registry is one per React, so a second React on the page never renders the first one's elements. No API changes. (#11096)
  • A swizzled ResizeHandle or LayoutPanel now finds the package's panel or handle beside it, and the reverse. When the region collapses, focus inside the panel moves to the handle and the panel goes inert. Before, each copy kept its own records of lent panels and handles, so the panel resized, but focus could drop to the page as it collapsed. No API changes. (#11131)
  • The package root and the component barrels no longer carry 'use client'. Inside a React Server Component, import {Card, Stack, Badge, Code} from '@astryxdesign/core' now renders the components that need no client code on the server, as their own modules intend; components that need the client stay client references. A Server Component that imports from the package root now builds with Next.js webpack. Client code renders the same as before. No API changes. To pass one of these components itself as a prop to a Client Component (for example components={{inlineCode: Code}} on Markdown), pass it from a 'use client' module. (#11106)
  • In iOS Safari, a tap that wobbles less than 5 px on content under a scroll-edge pan keeps its click. The pan now holds the finger only once it has moved 5 px along its axis. In Lab, in iOS Safari, a tap on a pushed NavigationStack screen that drifts less than 5 px toward the back swipe now runs; one that drifts 5 px or more toward it still loses its click. (#10829)
  • A component built on useScrollableArea, such as ScrollableArea or BottomSheet, no longer renders again when focus moves between two descendants of a fitting viewport just after the component's own update. (#11135)
  • Toast ids are now one sequence across the package and a swizzled copy of useToast. Before, each copy counted from 1, so a toast from a swizzled Toast and a toast from the package could share an id in the same queue, and dismissing one removed the other. No API changes. (#11092)
  • A windowed Table keeps windowing when a text-size, zoom or theme change makes every row taller than rowHeight. It windows at the height the rows measure, instead of rendering every row, and warns in development. Rows of unequal height still render every row. (#11000)
  • Without a LayerProvider, toasts from a swizzled useToast and from the package now show in one fallback stack. Before, each copy mounted its own fallback container, so the page showed two toast stacks that overlapped. No API changes. (#11161)
  • Tokenizer: with hasEntriesOnFocus, picking a choice from the list shown on focus keeps the input focused and the list open, with the next choice active, so you can pick several in a row. The list closes when no choice remains, at maxEntries, or when you press elsewhere, Tab away or press Escape. A pick from typed search results still closes the list. (#11031)
  • Typeahead and Tokenizer keep a dismissed menu closed when a search or focus bootstrap that was still running answers afterwards. Closing the menu with Escape, an outside click, Tab, or moving focus away also clears the busy indicator and drops a search still waiting on its debounce. A late answer for the same text is kept and shown the next time the menu opens, without searching again (reopening while that search still runs waits for its answer); an answer for text the person has since changed is dropped. Previously the late answer reopened the menu after it had been dismissed. (#8778)
Documentation
  • AppShell's guidance on naming its navigation landmarks now says to pass label to TopNav and aria-label to SideNav. SideNav has no label prop; it has a translated default name, and aria-label renames it. (#11151)
  • Add hook documentation and interactive table cell truncation example block for useTruncation, demonstrating responsive string truncation and accessibility tooltips. (#10555)
  • InternationalizationProvider shows its examples in reading order: load a shipped locale, mirror the layout for right-to-left text (a new code example), override one string, then the calendar examples. Each live example is titled after its code example, so the two lists match. (#11094)
  • LinkProvider docs say what component receives, including the to prop that router components read, that a link's own as or a nearer provider wins over it, and that a disabled Link does not use it. (#11065)
Other Changes
  • Internal: Core's internal finger-scroll reader accepts a ref that names the document, so Lab's ChatVirtualizer can watch the page's own scroll when it attaches to document.scrollingElement. Apps import nothing new. (#10883)
  • Internal: MobileNav keeps its dialog rendered from the open until its delayed close has run through the layer runtime's presentation hold (Layer/presentationHold.ts). No behavior change. (#8590)
  • Internal: useChatStreamScroll's page-scroller rules move to one owner module: whether a container scrolls the page, where its visible area starts, and where its scroll events fire. The hook behaves as before, and the undocumented @astryxdesign/core/internal/page-scroller entry gives the same rules to Lab's ChatVirtualizer. Internal entries are outside the public API and its compatibility promise. (#11160)
  • Internal: Core's reorder controller finds a collection's rows through an internal rows reader, so a later change can reorder plain elements. List behaves as before, and apps import nothing new. (#11199)
Contributors
Thanks to everyone who contributed to this release:

0.7.13

New Features
  • Tokenizer forwards BaseTypeahead's menu and onOpenChange in its inline presentation, and its handle gains open() and close(). A token whose own button calls open() with a dialog-role menu opens the dialog, and Escape returns focus to that token: focus that a press puts on a token's control, and the menu's focus return, stay there instead of moving to the input. The sheet presentation keeps its own sheet. (#10624)
  • Typeahead: Backspace or Delete on the selected Token clears the value, as the clear button does, when the clear button shows: it calls onChange(null), announces the cleared value, and moves focus to the empty input. Without hasClear, the keys start editing, as a click does. (#10847)
Fixes
  • A swizzled component and the package's components now announce through one pair of live regions: messages from both join the same frame, and a copy no longer mounts a second pair that screen readers would read twice or skip. The modal announcement route is shared the same way. No API changes. (#10996)
  • BottomSheet: a finger's pull on the sheet's content at a scroll edge cancels the content's native pan as soon as the pull reaches a tap's wobble (5 px), before the sheet's own drag begins at 8 px. In iOS Safari the first touchmove a page keeps committed the touch to the content's scroll, so a slow-starting swipe down rubber-banded the content under the finger while the sheet moved beside it. A tap that wobbles less than 5 px keeps its click, while a tap that wobbles 5 to 8 px toward the edge now loses it. A real scroll is never cancelled. A mostly sideways swipe on a horizontal row is not cancelled before the sheet's drag begins; a first move past 8 px starts the drag in any direction, as before. (#10033)
  • A swizzled overlay that carries its own copy of the layer runtime now shares the package's: one layer stack, one modal outlet order, one gesture counter, and one record of outside dismissals, popover show and hide operations, layer surfaces and press claims per page. Before, such a copy kept its own, so Escape over a swizzled HoverCard inside a package Dialog could close the Dialog too, and the two copies could race each other's popover operations or miss each other's outside presses. No API changes. (#10998)
  • A disabled Link stays announced as disabled, with its own role, when the caller also passes aria-disabled or role. Before, those caller props replaced Link's own, so aria-disabled={false} announced a disabled link as enabled, and role="button" announced a button that does nothing. (#11030)
  • Markdown's public parser drops every data: link and image URL, and <Markdown> renders data: links and images as source text. (#11020)
  • Carousel snap paging: in Safari, a held row's stops and span stay on each item's start edge when the settle moves between an item's rect read and its translate read. (#10992)
Documentation
  • Add hook documentation and interactive sparkline example block for useDirection, detailing render-time direction handling and CSS logical properties best practices. (#10547)
  • InternationalizationProvider has a calendar example: the provider's calendar prop shows a Calendar and a DateInput in the Japanese or Buddhist calendar, and the value stays a Gregorian ISO date. Both calendars work without Temporal. (#10135)
Other Changes
  • Internal: Table's row virtualization now runs on one shared list-windowing module inside Core, which later long lists will reuse. The undocumented @astryxdesign/core/internal/virtualization entry gives Lab the same module. Table's behavior and public API do not change. Internal entries are outside the public API and its compatibility promise. (#10810)
Contributors
Thanks to everyone who contributed to this release:

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: