What's New

Release notes and changelog for all packages.

0.6.6

New Features
  • Add a shared upload icon, and use it for FileInput's upload affordance instead of the directional arrowUp Themes draw upload through icons.upload, separately from arrowUp, so sort arrows and every other arrowUp use stay unchanged. Every bundled theme and theme template draws upload in its own icon style. FileInput keeps its icon size, placement, color, and accessibility in both modes; a theme with no upload artwork shows the default upload-into-tray glyph there.
    A complete IconRegistry may still omit upload in this release. The next minor makes it required, so add an upload entry to any registry you type as IconRegistry.
  • BottomSheet is a container, like Dialog. A new padding prop takes a spacing step, and a theme's padding on bottom-sheet now pads the sheet's content box through container tokens instead of padding the panel. The padded content box publishes its inset, so a Section that is the sheet's only child, and bleed children such as Table and Divider, align against it. With neither set, the content box stays unpadded as before.
  • ComplexSelector can hang off a control the caller renders. A new renderTrigger render prop renders the control the popup hangs off — a glyph in a list row, a chip, an icon button — in place of the selector's own field and button. Spread the given props onto it; the popup is anchored to it, keeps its dialog label from label, opens on click or ArrowDown, and returns focus to the control on close. The existing handleRef and onOpenChange work unchanged beside it. Off by default; existing selectors are unchanged.
  • ContextMenu takes triggerAs (div | span) so a reference inside prose can own a context menu without breaking the text flow.
  • Export the canonical 56-token StyleX dataVars group for CSS-capable data visualization consumers.
  • Export decodeMarkdownCharacterReferences from @astryxdesign/core/Markdown/parser and @astryxdesign/core/Markdown It decodes character references the way Markdown renders them — ©, &[#169](https://github.com/meta/astryx/pull/169);, and © become ©; unknown names and references without their semicolon stay as written — using the same table Markdown uses. It works on plain text, so leave code and backslash-escaped references out. The parser subpath has no use-client boundary, so server code can call it.
  • Add DropdownMenuGroup, a titled role="group" of rows for compound-mode menus. The items data API could title a group ({type: 'section', title, items}); a menu written with children — checkbox rows, radio groups, rows mounted only while open — could not. DropdownMenuGroup (also ContextMenuGroup and BreadcrumbMenuGroup) renders a role="group" named by its heading through aria-labelledby; the heading shares the data mode's typography and astryx-dropdown-menu-section-heading theme target, is not a menu item, and is skipped by arrow keys and typeahead. Existing menus are unchanged.
  • The message a component shows when a query matched nothing is now emptySearchText everywhere, and it takes a ReactNode. Selector, MultiSelector, and CommandPalette already called it emptySearchText and already accepted a node. Tokenizer, Typeahead, BaseTypeahead, and each ChatComposerInput trigger called it emptySearchResultsText and accepted only a string — so the same product could offer a "no results, create one" row in one component and not in its neighbour, and a builder who learned one had to discover the other.
    Nothing breaks. The type only widens, so every existing value stays valid, and emptySearchResultsText keeps working exactly as released. Set both and emptySearchText wins, with a development warning. Migration is the name alone.
    Deprecation lifecycle (spec:AST-017 FR28, FR31) — removal only in a later minor whose frozen manifest carries both ids of a pair:
  • The layer runtime owns the viewport inset: one gutter, one cap, one fallback order, and one place an app declares a floating bar. Every anchored layer — Popover, DropdownMenu and its submenus, Typeahead, Tooltip, HoverCard, the selectors — now keeps the same gutter from each viewport edge (the spacing-4 step or the device safe-area inset, whichever is larger) and is capped to the viewport. Four components used to carry their own copies of that gutter, and they had drifted.
  • Add the first-party Markdown heading-links module. createMarkdownHeadingLinks() is exported from @astryxdesign/core/Markdown/plugins and gives every built-in h1–h6 a collision-safe generated fragment plus an accessible inline trailing # copy button, including headings nested in blockquotes and lists. Its frozen, versioned entry carries the namespace and safe URL base across compatible Core package copies without module-local state. The heading row uses useContainerReveal: the button is hidden at fine-pointer rest, reveals on row hover or keyboard focus, and follows the canonical coarse/touch behavior. An unmodified tap, click, Enter, or Space copies the canonical URL without navigating, scrolling, or mutating the hash and briefly shows a check confirmation; failures stay silent. The same opaque plugin entry keeps Markdown-derived Outline aligned, supports Unicode NFKC slugs, an optional caller-owned namespace and safe permalink URL base, and leaves default Markdown plus custom heading renderers unchanged.
  • Markdown: nested lists draw a different marker at each depth Bulleted lists cycle disc, circle, and square, and numbered lists cycle decimal, lower-alpha, and lower-roman, by how many lists of either kind enclose them, so each level can be told apart from the levels beside it. Numbering keeps each list's start and items. List and ListItem keep their public marker styles.
  • Markdown plugins: read what a plugin declares, and render one plugin node as Markdown does getMarkdownPluginCapabilities(plugin), from @astryxdesign/core/Markdown/plugins, reports whether a plugin declares syntax and whether it declares a transform, and nothing else; plugin entries stay opaque. MarkdownPluginNodeRenderer, from the new client-only @astryxdesign/core/Markdown/plugin-renderer subpath, renders one parsed extension node with the given plugins exactly as Markdown presents it — the plugin's renderer inside the same error boundary and suspense fallback, the same readable fallback text, and the same failure report — with no element of its own. Markdown's own output is unchanged.
  • DropdownMenu takes a trigger render prop: hang a menu off any control. trigger renders the control the menu opens from — an IconButton, a chip, an avatar, a list row — and hands it DropdownMenuTriggerProps to spread: the press model, the keyboard opens, the toggle click and the ARIA wiring. The menu is named by that control through aria-labelledby. button and trigger are mutually exclusive (a dev warning).
  • Menu arrows wrap and PageUp/PageDown page. In DropdownMenu, ContextMenu and DropdownMenuSubMenu, ArrowDown on the last row wraps to the first and ArrowUp on the first to the last, as macOS menus do (Selector keeps clamping like a native select). PageDown and PageUp move to the last and first fully visible row of a scrolling menu, and pressed there again one viewport further, never wrapping. ArrowUp on the trigger opens the menu with the last row highlighted. The key that opened the menu no longer activates the first row through its auto-repeat, and typeahead ignores a key that is part of an input-method composition. useListFocus gains hasPaging.
  • DropdownMenuItem takes href: a menu row that navigates is a real link. DropdownMenuItem (and a data-mode item) takes href, target and rel. The row renders as the anchor itself, with role="menuitem", routed through LinkProvider, so a ⌘-click, Ctrl-click or middle click keeps the browser's meaning and skips onClick; a plain click runs onClick, closes the menu and navigates. The touch sheet renders the same item as a link row. onClick now receives the click event. Enter and Space in every menu synthesize a click that carries the key's modifiers.
  • DropdownMenu takes menuMaxHeight to lift the 300px cap for a menu that must fit its rows; the viewport still bounds it.
  • Menus and pickers act on the row under the pointer at release, and the highlight follows a held finger or mouse. DropdownMenu, ContextMenu, DropdownMenuSubMenu, Selector and the menu bottom sheet share one press model, the one macOS and iOS menus use: the row under the pointer when it is released is the row that acts, and the highlight follows a held pointer across the rows. A finger that lands on one row and lifts on another acts on the second — once; the click the browser aims at the first row is swallowed. A mouse released outside a menu closes it; a finger released outside leaves it open. A menu whose rows fit declares touch-action: none so a slide stays a slide; one that scrolls lets the browser pan it and ends the gesture. Menu rows no longer paint a pressed look where hover does not exist. New public hook: useMenuPress.
  • A mouse opens a DropdownMenu on press and can drag straight into it; a finger held on the trigger opens it with the finger down. A DropdownMenu trigger now opens its menu on a mouse press-down, and a drag from the trigger into the menu that lets go over a row picks it, as macOS menus do. The release of the opening press acts only after the pointer has entered the menu or the press has lasted about a third of a second, so a menu that opens under the pointer never picks a row nobody chose. Pressing the trigger of an open menu closes it without reopening in the same gesture. A tap still opens through its click; a finger held on the trigger for half a second opens the menu with the finger down, and a slide then picks. useMenuPress gains onTriggerPress, triggerProps, isTriggerClickFromPress and longPressDelayMs.
  • DropdownMenuSubMenu drills in on a phone instead of opening a flyout.
    When a coarse pointer opened the menu, a sub-menu row replaces the menu's rows with its own and a "Back to <parent>" row, in the same box; Back, Escape or ArrowLeft return to the row. Works in compound and data mode, inside DropdownMenu and ContextMenu; presentation (flyout | drill-in | adaptive) overrides the policy.
  • MultiSelector can offer a Create "<query>" row for a search that matches nothing. With hasSearch, the new hasCreate switch puts a Create "<query>" row first in the list when the trimmed query equals no option label under the search's own case-insensitive matching and the options have loaded. Picking it, or Enter with nothing highlighted, calls onChange with the query appended to the value and a second argument {type: 'create', query} (exported as MultiSelectorChange), then clears the search; the caller adds an option for the new value in that same update. Every other change passes no descriptor, so existing one-argument handlers are unchanged. hasCreate without hasSearch warns in development and offers nothing. Off by default.
  • MultiSelector can hang off a control the caller renders. A new renderTrigger render prop renders the control the panel hangs off — a glyph in a list row, a chip, an icon button — in place of the selector's own field and button. Spread the given props onto it; the listbox is anchored to it, named by label, takes focus on open, and focus returns to the control on close. handleRef (open/close/toggle/isOpen, the ComplexSelectorHandle shape) and onOpenChange let the caller open the panel from a keystroke elsewhere and observe every open and close. All three are off by default; existing selectors are unchanged.
  • Sub-menu flyouts stay open while the pointer travels toward them, and a press on a sub-menu row opens it without ever closing the menu. In DropdownMenuSubMenu the flyout now stays open while the mouse moves from the row toward the flyout inside the triangle to its near edge, and closes after the existing delay once the pointer has left both the row and that triangle, so a diagonal path to the flyout no longer folds it. A click or release on a sub-menu row opens its flyout; on an open one it confirms the flyout and moves focus into it instead of toggling it shut, as macOS sub-menu rows do. useMenuHover gains flyoutRef and passes the leave event to onMouseLeave.
  • Touch press model: under a coarse pointer the bare :active arm is dropped and a delegated, document-level controller paints the press the way a native list does — nothing for 150 ms, then the full pressed overlay on the next frame; cancelled with no fade by 10 px of travel or by a scroll claiming the gesture, and dead until a new touch; a tap shorter than the delay paints at the lift; the release fades over 200 ms, a real fade on every surface: the pressed overlay is the pressed token at --astryx-press-alpha, a registered custom property (@property, syntax <number>) the release arm animates 1 → 0, declared once by the shared overlay styles as --_press-paint and read by whatever paints it. The controller writes data-astryx-press="on"|"fading" on the nearest element marked data-astryx-pressable, which every Astryx surface that paints a press now carries; a mouse keeps :active. Public API for a local pressable: usePressFeedback() from @astryxdesign/core/hooks (returns the marker to spread; installs the controller on first mount) and interactionOverlayStyles from @astryxdesign/core/utils (compose one of its variants on the marked element). A press is themed through --color-overlay-pressed, which the hold, the flash and the fade all read.
Fixes
  • Selector and MultiSelector announce the empty-state message they actually show, and announce it on every path that reaches one. Two defects, one cause — the live region was fed from the props instead of from what rendered:
  • Typeahead, Tokenizer, and PowerSearch (which composes Tokenizer): clicking the search/combobox input after the dropdown closed without a blur now reopens it. BaseTypeahead only ever opened its dropdown in response to a real focus event. Any flow that closes the dropdown while leaving the input focused — selecting a result (which re-focuses the input internally after clearing it), pressing Escape, or a composing component (PowerSearch's token add/remove, e.g.) imperatively re-focusing the same input once it's done — dispatches no new focus event, since focus() is a no-op on an element that's already the active element. The input looked focused and clickable, but clicking it did nothing until the user clicked elsewhere first and back.
    BaseTypeahead now also opens on click, specifically when the input was already focused before the click began (checked at pointerdown, before the browser's own default action moves focus — a click that itself just caused the input to gain focus is left to the existing focus path, so the two don't double-fire a bootstrap fetch on a single first click).
    Only Typeahead and Tokenizer compose BaseTypeahead directly — Selector, MultiSelector, CommandPalette, and DateTimeInput use their own separate combobox implementations (which only follow BaseTypeahead's conventions, not its code) and are unaffected by this change.
    Fixes #6845.
  • Card: yield to a flex row or grid track instead of widening it to the card's content. A card no longer holds its row or 1fr grid track at its min-content width, so a long unbroken value (an ID, a hash) inside a card can no longer push side-by-side cards past a phone screen. Cards that fit are unchanged. Content that cannot wrap is clipped at the card edge, as it already was for cards with an explicit width; truncate such values with Text maxLines={1} and give wide content its own scroll region. An explicit width is now the card's preferred width in a row rather than a floor. To hold it, wrap the card in StackItem in a flex row, or set a consumer minWidth on the Card in Grid.
  • Chat: center inline tokens on the line box using 1lh and vertical-align top, fixing vertical misalignment against adjacent text and CJK characters.
  • Prevent disabled ClickableCard links from retaining an activatable destination.
  • Make Code's complete public API and theme target discoverable in component documentation.
  • Keep collapsible code blocks named and recoverable when header controls disappear, honor zero-pixel height limits, and document the public root ref.
  • Expose Collapsible open, disabled, position, and divided states to themes, and document grouped state ownership and root customization.
  • Preserve CollapsibleGroup context identity when a controlled string value is unchanged, avoiding unnecessary grouped-item rerenders.
  • Let CommandPaletteFooter wrap translated guidance on narrow screens, correct its composition example, and add owned audit coverage.
  • Field-based inputs (TextInput, Selector, DateInput, and the rest of the input family) can now be shrunk by their row: the Field root resets its automatic minimum size, so a filter bar of a search box and selectors no longer pushes past its container on phones
  • Defer a layer show() that arrives while another popover is mid show/hide, so a tooltip trigger regaining focus from a closing popover no longer throws InvalidStateError.
  • Markdown: read angle-bracket link destinations to their closing bracket Markdown now reads an angle-bracket destination as CommonMark specifies: parentheses inside the brackets are part of the address, so [a](<b(c>) links to b(c); an escaped bracket inside is part of it too, so <b\>c> is b>c; and a line ending inside the brackets makes the text no link. Unsafe schemes are refused as before.
  • Markdown keeps a backslash unless it escapes punctuation, and a backslash at the end of a line is a line break C:\Users\Ada rendered as C:UsersAda: any character after a backslash swallowed it. As CommonMark specifies, a backslash now escapes only ASCII punctuation (\*, \#, \\, …); before a letter, digit, space, or other character it stays as written. A backslash at the end of a line is a hard line break. Image alt text follows the same rule.
  • Markdown: cap list and blockquote nesting, so deep input cannot crash rendering Markdown now nests lists and blockquotes at most 100 levels deep, as it already caps emphasis; content nested deeper reads as text. A list or blockquote nested thousands of levels deep, as a crafted message can be, used to overflow the stack and throw while parsing.
  • Markdown: read a block quote marker as CommonMark does Markdown now reads a line that starts with up to three spaces and > as a block quote, whether or not a space follows the >: >quote, > quote, and >>> nested are quotes, as CommonMark specifies. These lines used to show as plain text with their > marks.
  • Markdown: start a new list when the bullet changes Markdown now starts a new list when a bullet list's marker changes — - a then * b are two lists — as CommonMark specifies, and as ordered lists already did when their delimiter changes.
  • Markdown shows character references such as &amp;, &copy;, and &[#169](https://github.com/meta/astryx/pull/169); as the characters they name Fish &amp; chips &copy; 2026 rendered with the references spelled out. Named references (every name in the HTML standard) and decimal or hexadecimal numeric references in text now render as their characters, as CommonMark specifies; inside inline code and code blocks they stay exactly as written. An unknown name or a reference without its closing ; stays literal, and a decoded character is never read as Markdown syntax.
  • Markdown: close a code span only at a backtick string of the same length Markdown now ends a code span at the next run of exactly as many backticks as opened it, never at part of a longer run, and reads runs of any length, as CommonMark specifies. `one two `` is one code span holding `` `, and four or more backticks open and close spans too. A run with no closer of its length stays text.
  • Markdown makes a hard line break from two spaces or a backslash before a Windows (CRLF) line ending Documents saved with CRLF line endings lost their hard line breaks: the carriage return sat between the trailing spaces or backslash and the line feed, so neither was recognized and the lines ran together. Both now break the line exactly as they do in an LF document, in paragraphs, links, and block quotes and while streaming; code spans, code blocks, and table cells are unchanged.
  • Markdown: read a code fence's language after spaces Markdown now reads a fenced code block's language as the first word of its info string after any spaces, as CommonMark specifies, so ~~~ js and ``` js are JavaScript blocks rather than blocks with no language. Fences written without a space read as before.
  • Markdown: give an image the plain text of its description as alt text Markdown now reads an image's description as inline content and uses its plain text as the alt text, as CommonMark specifies, so ![`a]b` *c*](u) has the alt a]b c rather than the raw source with its backticks and asterisks.
  • Markdown image alt text shows character references and escapes as the characters they name ![Fish &amp; chips](…) gave the image the alt text Fish &amp; chips, so a screen reader announced "amp". Alt text now resolves character references and backslash escapes the same way body text does, for inline, standalone, and reference-style images; an escaped & and unknown names stay literal.
  • Markdown: read an ATX heading indented up to three spaces as a heading [Markdown](/components/Markdown) now reads a heading line indented by up to three spaces, such as # Title, as a heading, as CommonMark specifies. Such lines used to show as plain text with their # marks, except at the very start of a streamed message.
  • Markdown: read a code fence indented up to three spaces as CommonMark does [Markdown](/components/Markdown) now reads a code fence indented by up to three spaces as a code block, and a closing fence may be indented the same way, as CommonMark specifies. Each code line loses as much indentation as the opening fence has. A closing fence has only spaces or tabs after it, so a line such as ```js inside an open block stays part of the code. Such fences used to show as raw backticks or tildes in a paragraph, and an indented closing fence left the block open to the end of the document.
  • Markdown: show a link whose destination opens with < but is no angle-bracket destination as text Markdown now shows [a](<b>c>), [a](<b), and [link](<foo\>) as text, as CommonMark specifies: a destination that opens with < must be one whole angle-bracket destination, with no line ending inside, even after a backslash. Such links used to fall back to a link to the whole text between the parentheses.
  • Markdown: keep lazy continuation lines fast in deeply nested input Markdown no longer slows to seconds on a deeply nested blockquote or list followed by a lazy continuation line, as a crafted message can be: checking whether the line continues a paragraph now reuses what the parser already read at each level, and checking a long line for a thematic break no longer copies it. Lists and blockquotes nest at most exactly 100 levels deep.
  • Markdown: find link destinations in linear time Markdown no longer searches the rest of the text for every link or image whose destination never closes, which made a message with many of them take seconds to render. Each parenthesis now pairs once per text, so such input renders in milliseconds; links read as before.
  • Markdown: decode character references and backslash escapes in link destinations, and close link text at an unescaped bracket A link or image destination now reads as CommonMark specifies: [x](https://a.com/?a=1&amp;b=2) links to https://a.com/?a=1&b=2, [x](a\)b) links to a)b, and reference definitions decode the same way. The URL safety check runs on the decoded destination, so an encoded unsafe scheme such as &[#106](https://github.com/meta/astryx/pull/106);avascript: is refused like the plain one. Link text and image alternative text close at the first unescaped ], so [a\]b](u) is a link with the text a]b.
  • Markdown: pair link text brackets as CommonMark does Markdown now pairs the brackets of link text as CommonMark specifies: link text may hold balanced brackets, so [a [b] c](u) is one link; the innermost bracket makes the link, so [a [b](u) links only b; and a link inside link text wins, so [a [b](u) c](v) shows the outer brackets as text instead of nesting links.
  • Markdown: a code span in link text hides its brackets Markdown no longer ends link text at a ] inside a code span, since code spans bind tighter than links (CommonMark). [`a]b`](/u) links the code a]b, and [`[x](javascript:y)`](/rel) links the code [x](javascript:y) to /rel rather than reading a link inside the code.
  • Markdown links and images go to their destination when the source also gives them a title [notes](https://example.com/notes "Release notes") linked to https://example.com/notes "Release notes" — an address that does not exist — and a titled image pointed at a source that could not load. A title after the destination, in double quotes, single quotes, or parentheses, is no longer part of the link or image address, and a destination in angle brackets may contain spaces. Content in any other shape keeps its meaning.
  • Markdown: keep content indented into a list item in the item after a blank line [Markdown](/components/Markdown) now keeps lines indented to a list item's content in that item after a blank line, as CommonMark specifies: a nested list, a fenced code block, or another paragraph under a numbered step stays in the step, and the numbering continues after it. Such content used to end the list, so the sub-items showed as a separate list and a step's code block showed as raw text.
  • Markdown: a list that mixes task and plain items shows each task item's checkbox In a list such as - [x] Done, - Plain, - [ ] Open, each task item now shows its own read-only checkbox, checked or open and named by its text, where its marker would be, and each plain item keeps its marker; the list stays one list. Before, the task items lost their checked state and showed bullets. Lists of only task items are unchanged.
  • Markdown: pair emphasis and strong markers by CommonMark's rules, so strong inside emphasis keeps its strong Runs of * and _ now pair as CommonMark specifies: by which side of a word they touch, by the nearest compatible opener, and by the rule of three. *see **bold** more* and *see **bold*** render the bold inside the emphasis, **bold *both*** renders the emphasis inside the strong, __foo, __bar__, baz__ nests, and an escaped \* inside emphasis stays literal. Before, the first matching marker closed emphasis early and left stray * or _ in the text. ***text*** still renders as strong around emphasis. Streaming closes an unfinished **bold before trailing spaces, so the partial text keeps its formatting.
  • Markdown: keep the indentation of a message's first line [Markdown](/components/Markdown) now keeps the indentation of a message's first line, as it already did for every later line: two bullets indented by the same amount stay side by side, an indented numbered list keeps each item, and an indented table keeps its columns. A message that started with indented content used to render it differently from the same text after its first line.
  • Markdown: end a list at a thematic break [Markdown](/components/Markdown) now reads a line such as * * * or - - - after a list item as a thematic break that ends the list, as CommonMark specifies, rather than as another item holding a nested list.
  • Markdown: check a line's trailing spaces in linear time [Markdown](/components/Markdown) no longer slows to seconds on a line holding a long run of spaces before its last word, as a crafted message can: deciding whether trailing spaces make a hard line break now counts them from the end of the line instead of matching a pattern that retried from every space. Line breaks read as before.
  • A DropdownMenu returns focus to its trigger after a pointer dismissal, without painting a focus ring. [DropdownMenu](/components/DropdownMenu) used to blur its trigger after a pointer pick or an outside press, dropping focus to the page so the next arrow key went nowhere. Focus now returns to the trigger with the focus ring suppressed after pointer input, as the bottom-sheet presentation already did, and stays visible after a keyboard pick. A press outside that landed on a focusable control keeps focus there.
  • A nav or menu trigger disabled while a hover is in flight no longer opens its surface. Hover intent schedules an open after a short delay. Disabling the trigger in that window left the scheduled open to land anyway, on a surface whose handlers were already inert — so it opened and nothing could dismiss it. The pending intent is now abandoned when the integration is disabled.
  • A Layout nested in AppShell content, or in any other Layout, no longer inherits the outer Layout's padding. Its header, panels, content, and footer keep their default inset (or the enclosing Card, Section, or Dialog padding) instead of rendering flush against the content edge. An explicit padding on the nested Layout still wins.
  • Restore Outline's visible keyboard focus indicator.
  • Refresh stale cached field entries when [PowerSearch](/components/PowerSearch) reopens an already-focused input after its search source changes (#6845).
  • Preserve consumer className on ToggleButton while retaining its theme classes.
  • Navigation URL safety: refuse a data URL with spaces before its media type The shared URL safety check now ignores spaces after a URL's scheme before it compares the scheme, as a data URL's media type does, so data: text/html,… is refused like data:text/html,…. In Markdown this also refuses links, images, and angle autolinks whose destination decodes to that form, such as data:&[#32](https://github.com/meta/astryx/pull/32);text/html,…. Accepted URLs are returned as before.
  • Let chat follow reach the bottom when browsers round scroll offsets.
  • Toolbar's center slot no longer clips its content, so focus rings, box-shadows, and the selected-tab indicator of a TabList in centerContent are drawn in full. Center content that cannot shrink and is wider than the space between the start and end slots now overflows it instead of being cut off.
  • Forward accepted DOM props such as id, data-*, and onClick to the Typeahead and Tokenizer root elements. Preserve existing ref, styling, and data-testid targets and Typeahead's built-in focus and edit behavior inside InputGroup.
Other Changes
  • emptyText and emptySearchText accept a ReactNode, but the region spoke the value only when it was a string and announced the built-in default otherwise. A product that put a link or a "create one" row in the dead end showed one message and announced another, so the screen-reader user was told something the sighted user was not reading.
  • An empty result that arrived after the keystroke — an async load landing with nothing that matches an active query — was never announced at all. The message sat on screen and the region stayed silent.
    Both components now read the rendered message out of the DOM and announce that, from one place that watches the panel's state rather than the keystroke. An element is announced as written, text a child component generates is announced correctly, and anything marked aria-hidden is left out of the announcement exactly as it is left out of the screen. A loading panel still announces nothing.
  • deprecation DEP-0001 / cleanup CLN-0001 — [Tokenizer](/components/Tokenizer).emptySearchResultsText
  • deprecation DEP-0002 / cleanup CLN-0002 — [Typeahead](/components/Typeahead).emptySearchResultsText
  • deprecation DEP-0003 / cleanup CLN-0003 — [BaseTypeahead](/components/BaseTypeahead).emptySearchResultsText
  • deprecation DEP-0004 / cleanup CLN-0004 — ChatComposerTrigger.emptySearchResultsText
  • An explicit width on [Popover](/components/Popover) and menuWidth on [DropdownMenu](/components/DropdownMenu) or [Typeahead](/components/Typeahead) render at their size up to the viewport. They used to be capped to the room beside the trigger, so a 352px menu opened from a control near a panel edge rendered 274px wide.
  • A layer that does not fit beside its trigger flips; one that fits on neither side keeps its size and slides into view while its trigger is on screen. Once the trigger has left the viewport the layer holds its position and size instead of chasing the edge.
  • An app that floats a persistent bar over a viewport edge — a phone navigation bar — declares it once, as inset on the [LayerProvider](/components/LayerProvider) it already mounts: <[LayerProvider](/components/LayerProvider) inset={{blockEnd: 56}}>. Every anchored layer then ends above the bar, and the toast viewport rises by the same amount, so one bar is declared once for both. Every edge defaults to zero, so nothing moves by default; an existing toast.inset keeps its meaning as the toast-only override.
    One additive prop ([LayerProvider](/components/LayerProvider).inset, type LayerInset); no other prop, type, or default changes. spec:AST-059 holds the decisions; the Core/Layer stories show each behavior.
Contributors
Thanks to everyone who contributed to this release:

0.6.5

New Features
  • Stop bundling translator-only descriptions with the built-in English fallback and add compact generated string-map modules for every shipped locale. Existing rich JSON catalog exports remain unchanged.
  • Popover and usePopover take a padding prop on the spacing scale (matching Card and Stack). padding={0} paints a flush surface for content that owns its own edges, such as a list of rows or a header with a rule; the default rung (3) is unchanged.
Fixes
  • Button no longer overflows narrow rows: a labelled button can shrink below its label width and truncates the label with an ellipsis, while icon-only buttons stay square
  • Prevent an empty Tokenizer input from creating a blank trailing row.
  • SegmentedControl's default hug layout is now capped at its container width, and its segments shrink and truncate their labels instead of overflowing narrow cards and phone rows
  • SelectableCard: keep disabled cards in sequential focus navigation with aria-disabled and gated interaction handlers.
  • Selector's one-line trigger matches its size token when the theme's --spacing-5 is taller than the token can hold, instead of overshooting it.
  • Switch: announce busy/loading states through the persistent [useAnnounce](/components/useAnnounce) live region and localize the announcement via @astryx.switch.loading.
Contributors
Thanks to everyone who contributed to this release:

0.6.4

New Features
  • Add Timer for standardized elapsed durations without React tick renders. (#6438) Use [Timer](/components/Timer) for active-operation elapsed time. It starts from mount by default, accepts an earlier Unix-millisecond startTime, offers elapsed and clock formats with adaptive cadence, and matches Timestamp typography props.
  • DialogHeader: expose the start- and end-content wrappers as theme targets (#6415) Adds dialog-header-start-content and dialog-header-end-content so themes can style the existing content-slot wrappers without relying on their DOM positions. The end-content slot also contains the optional close button. Default layout and behavior are unchanged.
  • [DialogHeader](/components/DialogHeader) title and subtitle now accept any ReactNode, not only strings. A title can carry inline markup and still renders inside the focusable h2 that receives focus on open and names the Dialog; the accessible name is the title's text content. A subtitle can carry inline content such as a [Link](/components/Link). String callers are unchanged. An empty-string, boolean, or nullish subtitle renders nothing, and a numeric 0 subtitle now renders inside the subtitle text.
  • [DropdownMenuItem](/components/DropdownMenuItem), [DropdownMenuCheckboxItem](/components/DropdownMenuCheckboxItem) and [DropdownMenuRadioItem](/components/DropdownMenuRadioItem) forward a ref to the row root (#6687). The ref reaches the element carrying role="menuitem" (or menuitemcheckbox / menuitemradio), the way [Item](/components/Item) and [DropdownMenuDivider](/components/DropdownMenuDivider) already forward one, so a menu row can be registered with an element-keyed observer or overlay — an IntersectionObserver for an impression, a measurement, a debug outline — without a wrapper between role="menu" and the row.
  • Add presentation to DateInput, DateTimeInput, and TimeInput (spec:AST-043) (#6628).
    presentation names every picker surface, distinguishing Astryx's desktop surface, Astryx's bottom sheet (including a new TimeInput sheet), the browser/OS picker, and — for TimeInput only — a plain typed field. DateInput and DateTimeInput accept five values: 'popover' | 'bottom-sheet' | 'native' | 'adaptive-bottom-sheet' | 'adaptive-native' (default). TimeInput accepts those five plus 'text-input', the typed field on every pointer, because that is the surface its released nativePicker="never" already was. presentation="native" always shows native; adaptive-native keeps the released native fallbacks.
    nativePicker is deprecated but keeps working exactly as released (touch→adaptive-native, always→native, never→adaptive-bottom-sheet, or text-input for TimeInput); presentation wins when both are set. astryx upgrade ships migrate-native-picker-to-presentation for static callsites.
  • [List](/components/List): add edgeCompensation="inline" to compensate for item content inset within container padding (#2626) [ListItem](/components/ListItem) insets its content by a density-dependent horizontal padding, so a list under a section heading reads as misaligned and consumers reach for negative-margin custom CSS. edgeCompensation="inline" on [List](/components/List) cancels, per inline edge, the smaller of that inset and the container's published padding on that edge; zero-padding and full-bleed surfaces therefore stay in place, asymmetric container padding never over-cancels an edge, and headers, hover backgrounds, and selection backgrounds keep their existing geometry.
    [Item](/components/Item) now publishes its inline inset as --_item-inset-inline and derives its own paddingInline from it, and the clamped cancelling margin reads the same variable — so the cancel tracks density and theme overrides instead of mirroring hardcoded values. Themes that set paddingInline on item feed the variable automatically via the derived var registry.
  • Markdown: add the first-party soft-breaks plugin (#6459) Use markdownSoftBreaksPlugin from @astryxdesign/core/[Markdown](/components/Markdown)/plugins to render soft line endings as hard breaks without preprocessing source. The plugin matches the real remark-breaks package through Astryx's supported adapter path while keeping code and other opaque content unchanged.
  • Table: add a selection-aware bulk-actions wrapper that consumes [useTableSelectionState](/components/useTableSelectionState) output while keeping the selection plugin behavior-only. (#6474)
Fixes
  • Preserve authored heading and text component styles when theme adaptations change the type scale (#6710)
  • AvatarGroup keeps its overlap when avatars are wrapped in a HoverCard or Tooltip. Every avatar and the overflow indicator now take the overlap margin, and the group pads its start edge to match, so the overlap no longer depends on each avatar being a direct child of the group (#6736).
  • Avatar initials skip punctuation: each word's initial is its first letter, digit or emoji, so Northwind Workbench (automation) renders NA instead of N( and “Ada” Lovelace renders AL instead of “L. Words with none of those, such as a lone -, are ignored, and a name made only of punctuation shows the default icon rather than a stray symbol (#6698).
  • Size an Astryx Icon without an explicit size to match its Button or IconButton: 16px for small and medium controls, and 20px for large controls. (#5762)
  • [ChatComposerInput](/components/ChatComposerInput): an empty input no longer shrinks by 8px when isDisabled flips to true, which shifted anything bottom-aligned beside it (e.g. a send button in a grid row) (#6654). The root's minHeight was set to the shared line-height only, not the padding editable and placeholder both add on top of it — normally immaterial, since the editable region reserves its own padded box even when empty. A disabled, empty contentEditable region stops reserving that empty line at all in Chromium, and the absolutely positioned placeholder standing in for it doesn't contribute to layout height, so the root fell back to just the line-height and lost the padding. minHeight now explicitly accounts for both.
  • ChatComposerInput no longer scrolls for a short single-line draft with maxRows={1}. Removing vertical padding also keeps the empty input and placeholder aligned when disabled. (#6733)
  • Keep numeric zero aligned in ChatMessageBubble name and metadata slots. (#6600) The aligned wrappers are omitted for non-rendering scalar values (null, undefined, booleans, and the empty string), while numeric 0 remains visible inside the same inset as other slot content.
  • Render numeric zero when it is passed as the ChatMessageList empty state. A valid ReactNode should not disappear when the transcript is empty. (#6636)
  • Omit empty ChatMessageMetadata slots and their separators (#6637). Boolean and empty-string timestamp or footer values no longer leave a blank row or a stray dot. Numeric zero remains visible, and all delivery statuses keep their existing labels and icons.
  • Compose accepted onClick handlers with ChatSendButton's send and stop actions instead of replacing them (#6653). Consumers that used onClick to replace sending should move that logic to onSend, because both handlers now run.
  • Allow long ChatSystemMessage content to wrap within narrow chat layouts instead of crossing the container edge (#6655).
  • ChatTokenizedText now ignores empty token values so tokenized messages always finish rendering (#6679).
  • ChatToolCalls now displays custom group labels, keeps collapsed details out of keyboard navigation, adds visible focus treatment, and uses readable secondary text for neutral metadata (#6680).
  • Stop ChatLayout's scroll-to-bottom button from being a tab stop while it is invisible. At rest the layout's default scrollButton renders hidden, but opacity: 0 and pointer-events: none leave it in sequential focus navigation — so a keyboard user's first Tab into any chat landed on a control with no visible focus indicator (WCAG 2.2 SC 2.4.7), and Enter scrolled the transcript. The hidden state now also sets visibility: hidden, which the fade transition carries so the animation is unchanged; the visible button keeps its keyboard access. The pill's height and collapsed width now track --size-element-md instead of a hardcoded 32px, so a theme that retunes the element scale can no longer make the pill clip its own Button. ChatLayout's consumer docs also gain the density prop, which was undocumented, and drop the claim that density adapts automatically to container width — it never did. A Chromium evidence spec pins the hidden/visible/re-hidden keyboard contract and the pill's containment of its Button under a size-retuning theme, and the RTL applicability ledger records why ChatLayout and its scroll button have no applicable RTL dimension. (#6466)
  • Make a theme that styles chat-layout-scroll-button actually restyle the chat scroll-to-bottom pill. The documented target sat on the invisible full-width row that centres the pill, so a backgroundColor override painted a band across the chat dock while the pill kept the surface the theme asked to replace — and every automated check passed, because the override did reach an element. The target now rides the pill, which is what paints the fill, elevation, and radius (architecture:component-theming-surface INV4). The target keeps its name, stays a single target, and the component's props, DOM shape, ref target, and consumer passthrough are unchanged. A Chromium spec pins the placement and proves the repair by moving the target back and showing the pill go unstyled under a theme. (#6482)
  • Correct CheckboxIndicator theming, replacement-content, and focus guidance (#6745).
  • Align CheckboxInput theming and label-icon guidance with shipped behavior (#6747).
  • A CheckboxList option that is saving through changeAction now keeps its spinner, busy state, and re-toggle guard when another option is toggled before it settles (#6777).
  • Clicking a read-only CheckboxList option that has an onClick now fires that handler once, instead of re-dispatching the click until the browser's call stack overflows (#6777).
  • Give inert Citation references a supported accessible name, and document their linked and inert root contract.
  • CodeBlock no longer crashes on custom tokenizer types outside the built-in grammar (a dotted type such as keyword.control.sql threw from insertRule and took the whole block down). The generated ::highlight() name and --color-syntax-* custom property now pass through CSS.escape before entering the dynamic stylesheet, so every type the CSS parser accepts (dotted, digit-led, _private, non-ASCII) keeps its colour, and no token type can reach outside its own highlight rule. A rule the engine still refuses costs that type its colour, never the block. (#5528)
  • [Dialog](/components/Dialog) and 30 other components no longer lose their border and background resets in the shipped CSS. The sources used the border: 'none' and background: 'none' | 'transparent' shorthands, which StyleX's default property-specificity mode drops silently, so the declarations never reached astryx.css; a consumer that does not load reset.css saw the UA <dialog> frame. They are now the borderWidth / borderStyle / backgroundColor longhands. No API change.
  • Apply the same narrow blocked-scheme rule to native links, custom routers, clickable surfaces, and Markdown links. Rejected destinations stay visible without navigating or invoking a router, including structured URLs with a separate protocol. Ordinary URLs, safe custom schemes, downloads, and accepted router-object identity are preserved; Markdown image/resource policy is unchanged. (#5524)
  • Preserve Tailwind font weights when using the theme bridge. (#6479)
  • Ignore IME key events (isComposing or keyCode 229) in useHotkeys, even with allowInInputs enabled, without preventing their default behavior (#6773).
  • Keep hug-layout segmented controls content-sized in flex containers (#6643)
  • Keep a reopened top layer at the front of Escape dismissal order. (#6073)
  • Prevent ancestor text formatting and surface/group context from leaking into Layer content. (#6457) Layer content now starts with theme body typography and neutral text formatting. Core layer content no longer inherits accidental ancestor surface/group membership, including group-owned disabled state, selection, callbacks, and label associations. Intentional groups and required providers created inside the layer still apply. Unrelated contexts, explicit props, themes, and styling overrides remain unchanged.
  • [List](/components/List) with hasDividers no longer draws a divider after the last [ListItem](/components/ListItem). The last-item reset used the borderBlockEnd shorthand, which StyleX's default property-specificity mode drops silently, so it never reached the shipped CSS; it is now the borderBlockEndWidth longhand. (#6420)
  • Localize PowerSearch boolean operators in Japanese and Korean and use locale-appropriate ellipses in Chinese. (#6783)
  • Markdown: keep lazy continuation lines inside blockquotes and list items (#6752) Wrapped paragraph lines may omit repeated blockquote markers or list indentation without escaping their owning container. Nested, ordered, unordered, and task-list continuations now preserve their rendered structure, text projection, and source range.
  • Markdown tables now use the spacing-2 token (8px) on every header and body cell edge. The tighter inline spacing leaves more room for content in narrow reading columns while keeping rows comfortably readable.
  • Markdown: render escaped table pipes literally in code spans (#6642)
    A \| used to keep a pipe inside a table cell now displays as | in inline code, matching prose cells without exposing the structural backslash. Completed inline-code spans render only their parsed contents inside <code>, without source backticks; standalone inline code otherwise remains unchanged.
  • Markdown: table columns keep a content-derived width floor and headers stop truncating (#6708). A Markdown table in a narrow reading column no longer squashes every column to a few characters. Each column keeps a floor derived from its own content, measured in characters on the cell's text box, so a column is never narrower than its longest unbreakable token and cell padding does not eat into the floor. Identifiers, URLs, and inline code stay whole, header labels wrap instead of ellipsizing, and a table that is genuinely wider than its container scrolls in Table's own scroll region — which is now the table's only scroll viewport, accessible name, and keyboard stop.
  • Align titled sections in DropdownMenu and ContextMenu bottom sheets with their spacious action rows (#6694).
  • Keep MetadataList side labels readable beside long badges in narrow containers by allowing value columns to shrink, including numeric columns and custom label widths. (#6598)
  • PowerSearch: enum_list value menus now show every value instead of the typeahead default of 10. (#6481)
  • Selector keeps compact single-line triggers aligned with their size tokens, including icons and clear controls.
  • Name the no-search bottom-sheet [Selector](/components/Selector) listbox from the component's label so Chromium exposes it with an accessible name; the searchable sheet and popover paths keep their existing trigger relationship. (#6395)
  • Keep Tailwind bridge tokens reference-only so utilities follow the active theme without emitting competing runtime declarations.
  • Keep authored theme declarations inside their CSS boundaries. Drop only an unsafe declaration, preserve valid CSS values and legacy token generation, and continue compiling the rest of the theme. Runtime reports dropped declarations on the console; theme builds include them in the existing receipt warnings. CSS generators accept an optional warning-text array for build collectors, without a callback API or additional exported diagnostic types. (#5529)
Documentation
  • Document CheckboxList's isReadOnly prop, and separate the select-all block example's rows with hasDividers instead of placing a Divider inside the options list (#6777).
  • Clarify that CheckboxListItem reads isChecked and onCheck inside a CheckboxList without value (such as a select-all item), and requires value only when the parent CheckboxList has a value array (#6778).
  • Clarify that CheckIndicator is the selection mark itself and does not render persistent control chrome.
Contributors
Thanks to everyone who contributed to this release:

0.6.3

New Features
  • Show each shared InputClearButton's contextual action label in a tooltip. Clearable inputs now give sighted users the same specific action name already available to assistive technology. (#6354)
  • ChatComposerDrawer: add a collapsedSummary composition slot that replaces the complete Collapsed summary anatomy part when provided. Omitting it preserves the existing neutral Badge and label. (#5399)
  • DialogHeader: add end-content edge compensation control (#6465)
    DialogHeader now accepts endContentEdgeCompensation="inline" | "block" | "all" to select which axes of its existing end-content wrapper receive fixed compensation. Omitting the prop preserves the current automatic compensation whenever the close action renders.
  • Markdown: add native typed frontmatter metadata (#6381) Use createMarkdownFrontmatter() from @astryxdesign/core/[Markdown](/components/Markdown)/plugins to decode a document-start key/value block into typed metadata, keep unfinished streaming metadata hidden, and remove completed metadata syntax from rendered Markdown.
  • Markdown: add the core plugin protocol (#6340) Use createMarkdownPlugin() and Markdown's plugins prop to compose bounded source syntax, immutable typed AST transforms, and extension renderers. Import parseMarkdownAst() or parseInlineAst() from @astryxdesign/core/[Markdown](/components/Markdown)/parser when server code needs the canonical tree. The same ordered plugins work with parser entry points and Markdown-derived Outline items, while omitted or empty plugin lists preserve existing behavior.
  • Markdown: add a limited Remark compatibility adapter (#6345) Import createMarkdownRemarkTransform() from @astryxdesign/core/[Markdown](/components/Markdown)/remark to run one synchronous transform-only Remark plugin over the documented MDAST subset. Every invocation gets a fresh mutable tree and an isolated file, and each plugin's compatibility is proven by fixtures rather than assumed: async work, parser or compiler plugins, processor state, raw HTML, unsupported nodes, forged positions, and metadata Astryx cannot represent keep the last valid readable document and report one diagnostic. The adapter is a separate entry point, so it stays out of every bundle that does not import it.
  • Markdown: add a semantic code-fence transform helper (#6343) Use createMarkdownFenceTransform() to annotate declared fenced-code languages with typed extension data while standard plugin renderers own presentation and text projection. components.code retains precedence, and declined, missing, or failed proposals preserve Markdown's accessible, copyable [CodeBlock](/components/CodeBlock) fallback.
  • Markdown: add an immutable source-decoration helper (#6344) Use createMarkdownSourceDecoration() to attach non-visual metadata to every block a validated UTF-16 source range touches, and getMarkdownSourceDecorations() to read it back in a later plugin. It works through <[Markdown](/components/Markdown)> and Outline with no extra parser options, resolves independently of the order earlier transforms left blocks in, and appears on the settled document rather than on partial streaming chunks, so a decoration never appears and then vanishes. Metadata lives in one versioned Astryx-owned envelope that never merges foreign node data. Rendered output, copyable text, accessible names, heading ids, focus order, navigation, and source provenance are unchanged.
    Markdown transforms also got faster, and a plugin now always observes a fully immutable tree — including blocks a Core helper carried over untouched. Core-authored helpers now validate the nodes a caller's callback produced and run on a trusted path that skips the whole-tree validation and freezing applied to plugin-authored output, freezing walks only what a transform changed, a plugin list that contributes no inline syntax no longer costs anything per source character, and the helpers' per-match allocations and rebuilds are gone. The representative three-helper set now adds about 20 percent over an empty pipeline, inside its 25 percent budget, down from roughly 3.3x.
  • Markdown: add an immutable text-transform helper (#6342) Use createMarkdownTextTransform() to replace matching prose with typed Markdown nodes while preserving links, images, code, math, citations, and existing extension syntax as protected contexts.
  • Add pressed feedback to CheckboxInput, Collapsible, Link, Slider, Switch, TabList, RadioList, and unselected SegmentedControl items. Enabled controls paint --color-overlay-pressed on their interaction surface during pointer hold or drag; disabled controls and selected SegmentedControl items keep their existing surfaces. (#6380)
  • Let a TreeList item carry row styles (#6238) TreeListItemData gains xstyle, className, and style, applied to the item's row element, as the TreeList contract's per-item styling seam requires.
    [TreeList](/components/TreeList) takes rows as data, so nothing previously handed back the row's element. That prevents row-scoped primitives such as [useContainerReveal](/components/useContainerReveal) from installing the class and inline custom properties that jointly isolate each row's hover and focus state; applying the reveal to the whole tree would expose every row action at once.
    [Item](/components/Item) already accepts the same row styling props, so a list converting to a tree keeps its reveal wiring instead of having to mark the whole tree.
Fixes
  • Make overflowing BottomSheet text keyboard reachable with a named scroll-body tab stop. Add shared focus-time keyboard delegation to [useScrollableArea](/components/useScrollableArea): forward Tab may enter the first native link/button directly, while inputs, composite widgets, and nested scroll owners retain the viewport stop. Reverse traversal skips the delegated viewport; pointer/programmatic focus and content changes never trigger delegation. Sheet scroll containment now applies only while content overflows and uses the shared contain policy, which permits native edge feedback. (#6301)
  • Keep ChatComposer's public composition contracts aligned: custom inputs now submit the value they supply, disabled default editors expose their state to assistive technology, and an explicitly shown Stop action remains pointer-operable while editing is disabled. (#6398)
  • Keep collapsed [ChatComposerDrawer](/components/ChatComposerDrawer) content out of keyboard and assistive-technology navigation, and show the shared focus indicator on its disclosure control. (#6416)
  • Keep programmatic ChatComposerInput edits observable, deliver dropped files through onFiles, and let onPaste intercept text before default token conversion. (#6419)
  • Export ChatComposerTokenElementProps and forward supported span props and refs from [ChatComposerTokenElement](/components/ChatComposerTokenElement) (#6443).
  • Keep the chat dictation control disabled when speech recognition is unavailable, and preserve theme control over its clipping feedback (#6444).
  • Clip the resizable SideNav handle within the sidebar bounds (#6196)
  • scope the 16px text-control font-size floor to iOS with @supports (-webkit-touch-callout: none) inside the coarse-pointer query, so Android and touch-screen laptops keep the theme's type scale instead of an inflated 16px (#6085; fixes #6015)
  • Kbd: render the esc and return aliases with the same glyphs and accessible names as escape and enter (#5657) This partial fix for #5403 normalizes the two unambiguous aliases already accepted by [useHotkeys](/components/useHotkeys). Kbd now renders esc as Esc with the accessible name Escape, and return as ↵ with the accessible name Enter. Its lookup tables now also avoid prototype-chain collisions when rendering arbitrary key names. The platform-specific rendering contract for meta and display choice for space remain unresolved in #5403 pending separate API and design decisions.
  • LayoutFooter: add playground wrapper and default children for docsite preview (#6341) Prevents the properties-tab preview on the docsite from rendering an empty stage by wrapping LayoutFooter inside a Layout scaffold with representative footer content in the footer slot.
  • PowerSearch: switching the field or operator while the value menu is open now shows the new field's options instead of the old ones. (#6357)
  • Move focusable ProgressBar target marks outside the progressbar subtree (#6248)
  • Selector: collapse an option's mark column when its resolved selection indicator renders nothing. (#5619) Unselected rows using the default check indicator no longer lose label width to an empty wrapper. Selected marks and themed indicators that render an unselected state keep their space at the configured logical edge.
  • Slider marks inside the filled region use the fill color: marks at or behind the thumb in single mode, and marks between the thumbs in range mode, now paint with the accent fill color instead of the default mark color. Marks on the unfilled side are unchanged. (#6455)
  • Slider uses the track token for unfilled tick marks so marks and rails stay aligned across themes (#6461)
  • Spinner: animate the arc's dash offset instead of rotating the ring, fixing residual wobble on iOS Safari (#6311; fixes #6253) The earlier fix for #3617 added willChange: 'transform' to the rotating <svg>, which smooths the rotation's motion but does nothing about how WebKit rasterizes a rotating stroked shape's rounded cap on each frame. Rotating the whole ring still visibly wobbled on iOS Safari.
    Animates stroke-dashoffset on the stationary arc <circle> instead of rotating the <svg>, so the shape never rotates and WebKit never re-rasterizes the cap at an intermediate angle. Confirmed against a real iOS Safari device by the issue reporter.
  • Table: contain overscroll only while its inner viewport can scroll, so a fitting table no longer creates a dead scroll zone in its parent. (#6410)
  • Apply the theme's body font to the theme scope root. Generated theme CSS set font-family on headings, paragraphs, and code elements but never established a base font on the page, so components styled with font-family: inherit (SideNav items, Buttons) fell back to the browser default serif. The generator now emits font-family: var(--font-family-body) on :scope, which inherits through the tree. (#6450)
  • Keep ToggleButton callbacks synchronous and run pressed Actions through Button’s clickAction pathway, preserving callback cancellation and optimistic pending feedback. Omit the Action pathway for callback-only toggles and value-identified ToggleButtonGroup members, whose selection remains group-owned. (#6463)
  • Keep a ToggleButton's own isDisabled when its ToggleButtonGroup does not disable anything. The group always supplies an isDisabled boolean, so the previous ?? fallback never ran and an enabled group re-enabled a member that had disabled itself — the member selected on click, and a member carrying a tooltip stayed operable while looking unavailable. A disabled group still disables every member; it just cannot re-enable one. (#6356)
Contributors
Thanks to everyone who contributed to this release:

0.6.2

New Features
  • Markdown: add an opt-in math renderer (#6312)
    Supply components.math to parse $…$ inline math and $$…$$ display math. The renderer receives the delimiter-free expression as value and its placement as display: 'inline' | 'block', so applications can connect their preferred math typesetter without preprocessing Markdown or accepting raw HTML.
    Math is off unless the renderer is present. Direct parser callers can opt in with MathParseOptions ({math: true}) and incremental callers create IncrementalParseState<true> via createIncrementalState<true>(). Those overloads return InlineNodeWithMath or BlockNodeWithMath; default, legacy-set, math: false, and ParseOptions- annotated calls retain the existing InlineNode and BlockNode unions, so exhaustive consumers do not gain a case unless they opt in. Existing Markdown parsing and rendering stay unchanged by default; code stays opaque, escaped and unmatched delimiters stay literal, and inline plugins skip math. Incremental parsing preserves full-parse results when display math is nested in ordinary or task lists and blockquotes, including quote-depth transitions, with LF or CRLF and with source ranges enabled.
  • DialogHeader exposes theme targets for its header gap, title/subtitle gap, and close-icon size. (#6240)
  • Expose DateRangeInput preset theming targets (#6223)
  • Expose the Slider interactive control as a theme target (#6225)
  • Expose FileInput's upload icon as a mode-aware theme target (#5417)
  • Add a --spinner-arc-fraction public var to Spinner, so a theme can change how much of the ring the moving arc covers (defaults to 0.375, a 135deg sweep), the same way it already retheme diameter, stroke width, and color. (#5845)
Fixes
  • Adds the @astryx.chatTypingIndicator.* catalog keys so the lab ChatTypingIndicator can build its typing status from the translation runtime instead of English literals, joining names with Intl.ListFormat for the active locale. English output is unchanged. (#6220)
  • Spinner: the default assistive label now comes from the translation catalog (@astryx.spinner.loading) instead of a literal "Loading" in component source, so a localized app translates the status. An explicit aria-label and a visible string label still take precedence, in that order. (#6217)
Contributors
Thanks to everyone who contributed to this release: