@rcarls/rc-theme-material 0.6.0 → 0.7.0

package/CHANGELOG.md

@@ -1,5 +1,549 @@
 # @rcarls/rc-theme-material
 
+## 0.7.0
+
+### Minor Changes
+
+- f31cca3: Add `--rc-bottom-sheet-handle-offset` to position the handle indicator within its target. It
+  defaults to `50%`, which keeps the indicator centered. Set a length to keep the indicator in its
+  own row at the top of a handle that also holds the sheet's title.
+- 079e025: Standardize component styling contracts for the breaking 0.7 release.
+
+  BREAKING CHANGE: Rename the Markdown editor's `--rme-*` properties to
+  `--rc-markdown-editor-*`, `--rc-app-bar-background` to `--rc-app-bar-bg`,
+  `--rc-textarea-radius` to `--rc-textarea-border-radius`, the transfer-list
+  `--rc-transfer-list-panel-*` properties to `--rc-transfer-list-listbox-*`,
+  `--rc-chip-group-webkit-scrollbar-display` to
+  `--rc-chip-group-scrollbar-display`, and `--rc-text` to `--rc-field-text`.
+  Compatibility aliases are intentionally not provided.
+
+  BREAKING CHANGE: Replace `--rc-select-chip-padding-inline` and
+  `--rc-combobox-chip-padding-inline` with explicit `*-padding-inline-start` and
+  `*-padding-inline-end` tokens. Generated removable chips now reserve the full
+  remove target and its edge offset, so their indicator cannot overlap label text.
+
+  Add canonical app-bar elevation, transfer-list listbox radius, and textarea
+  line-action tokens. Add logical `rc-chip` inline-padding properties so themes
+  can implement Material's icon-aware spacing without overriding authored child
+  styles. Make `rc-field` consume the shared semantic token layer,
+  and place the `rc-chip` and `rc-search-bar` light-DOM structural styles in the
+  `rc-base` cascade layer so normal consumer rules override them.
+
+  Prevent decorative, `aria-hidden` trailing list content from intercepting a
+  whole-row action target, and keep segmented-list item geometry from leaking
+  into nested standard lists.
+
+  Remove unused Material navigation-rail toggle tokens and obsolete list-item
+  theme tokens. Register the segmented-button private theme seam and enforce
+  token ownership, documentation, removed-name, selector-budget, and cascade
+  layer contracts through the component architecture audit.
+
+- 4341311: Add reusable fullscreen dialogs and declarative dialog popup mode to `rc-select` and
+  `rc-combobox`. Dialog selection and creation are staged until Done, while close and Escape
+  discard the draft. Fullscreen surfaces follow the visual viewport under browser zoom and
+  software keyboards, and anchored popups now clamp to the visual viewport.
+- 5a7a1dd: `rc-dialog` gains `variant="side"`, a modal side sheet. The surface docks to the inline end at
+  full block size, pads every edge for the physical safe-area insets, and rounds only its start
+  corners. Like the fullscreen variant, it never moves or resizes. Theme it with
+  `--rc-dialog-side-inline-size`, `--rc-dialog-side-background`, `--rc-dialog-side-radius`, and
+  `--rc-dialog-side-shadow`. A landscape phone can now show a sheet's content beside the page
+  instead of in a bottom sheet that leaves only a strip of content visible.
+
+  A theme or consumer can now set a standard dialog's preferred width through
+  `--rc-dialog-inline-size`, which defaults to `fit-content`. Set it to `100%` for a dialog with
+  fluid content, such as a search field or a list, which otherwise shrinks to its minimum width.
+
+  The Material theme maps the side sheet to Material 3: `surface-container-low`, large leading
+  corners, and level 1 elevation. Its design guide documents side sheets, task dialog sizing, and
+  full-screen dialogs when the window is compact in either dimension. The React and Solid typings
+  accept the new variant.
+
+- 2c7c80a: Give `rc-dialog` a surface styling contract.
+
+  It exposed only `--rc-dialog-scrim`, so both themes drew the surface by selecting the native
+  `<dialog>` directly. It now installs a light-DOM base stylesheet, the same pattern as `rc-button`
+  and `rc-disclosure`, and exposes minimum and maximum inline and block bounds, padding, border, radius, background,
+  foreground, and shadow, plus fullscreen-specific padding and background for the two values that
+  variant genuinely needs of its own.
+
+  Fullscreen geometry, meaning position, size, margin, radius, and shadow, stays structural rather
+  than something a theme sets: filling the visual viewport is what keeps the surface correct under browser zoom
+  and a software keyboard.
+
+  Material's explicit block bound with `overflow: hidden` moved into the base layer rather than
+  staying a theme value. It exists because Chromium does not reliably clip a scrolling element's
+  own border radius at the scroll boundary, which is a correctness fix every theme needs.
+
+  `--rc-dialog-visual-viewport-left`, `-top`, `-width`, and `-height` are no longer documented as
+  theme properties. They are geometry the component writes while a fullscreen dialog is open:
+  readable if something inside the dialog needs the same measurements, but setting them does not
+  move the dialog. They are candidates for private `--_rc-dialog-*` names in a future revision.
+
+- 4b9bfe6: Give `rc-disclosure` and `rc-accordion` a public styling contract.
+
+  Both were styled by targeting the native `<details>` element directly, so neither exposed a
+  single `--rc-*` property and no theme could change them without rewriting theme CSS. They now
+  follow the light-DOM base pattern `rc-button` and `rc-listbox` already use: `rc-disclosure`
+  installs one structural stylesheet per containing `Document` or `ShadowRoot`, in `@layer rc-base`
+  behind a `data-rc-light-dom-base` sentinel, reading documented properties with UA-like defaults.
+
+  One recipe covers both supported child forms, a bare `<details>` inside `rc-accordion` and one
+  wrapped in `rc-disclosure`, so neither theme repeats the panel rules. `rc-accordion` owns only
+  `--rc-accordion-gap`.
+
+  Motion is opt-in. `--rc-disclosure-duration` defaults to `0ms`, so a disclosure with no theme keeps
+  the platform's snap-open behavior, and the height animation runs on `::details-content` behind a
+  `@supports selector()` check. This replaces Material's `60rem` `max-block-size` ceiling, which
+  clipped content taller than the guess and made every non-summary child its own animation unit.
+
+  **Fixes a missing expand affordance in the Material theme.** It set `display: grid` on the
+  `<summary>` and then styled `summary::marker`. Any `display` other than `list-item` drops the
+  marker box, so that rule styled nothing and the theme drew no replacement: a Material disclosure
+  had no disclosure triangle at all. The base layer never sets `display` on a summary, so the
+  marker survives. A theme may still change it, as Substrate does, but only alongside a
+  replacement affordance.
+
+- 19278d4: Group several native controls into one `rc-field` with a direct `<fieldset>`. Its `<legend>` names
+  the group and shows as the field label, each control keeps its own accessible name, and supporting
+  text describes the fieldset. The first text-like input or textarea is the primary control behind
+  `control`, `focus()`, and `data-populated`; focus moving between grouped controls keeps the field
+  focused; and `data-disabled`, `data-required`, and `data-invalid` reflect the whole group. New
+  read-only `group` and `controls` properties and a `data-group` host attribute support the mode.
+
+  The primary control grows and other controls attach before or after it. In Material, the legend uses
+  the floating label mechanics: it rests on the input line while the group is idle and its primary
+  input empty, and floats on focus or once that input has a value; a group with a control before its
+  primary input keeps it floated. Grouped placeholders wait for focus. Substrate colors an invalid
+  group's legend, and Win31 spaces it like a single field's label.
+
+- 6ec0857: Add `ordered` to `rc-list`. Visible items in an ordered list receive `aria-posinset` and
+  `aria-setsize` so assistive technology reports their position; no counters render, and authored
+  positions from a rendered slice of a longer list are kept.
+
+  Add an expandable `details` region to `rc-list-item`. A button marked
+  `data-rc-list-item-toggle` toggles it; the item wires `aria-expanded`, `aria-controls`, and the
+  region's `hidden` state, supports controlled `expanded` and uncontrolled `default-expanded`
+  state, and fires `rc-list-item-toggle`. Material styles the region as list supporting text.
+
+- c4ee38f: Draw Material disclosures as expandable list items. The summary now centers its
+  title in the 56px row and replaces the native disclosure triangle with a
+  trailing chevron that points down while closed and turns to point up while open,
+  the Android expandable-list-item affordance. The chevron keeps that direction in
+  RTL and vertical writing modes and stops turning under reduced motion.
+
+  Accordions now group their panels like a segmented `rc-list`: a 2px gap instead
+  of 8px, no outline, extra-small inner corners, and extra-large logical outer
+  corners on the first and last panel. A standalone `rc-disclosure` keeps its
+  outlined, uniformly rounded panel. This also removes a duplicate
+  `--rc-accordion-gap` declaration in `disclosure.css` that the accordion rule
+  always overrode.
+
+- 873592e: Add four directional motion tokens to the shared base contract:
+  `--rc-motion-effects-easing-enter`/`-exit` and
+  `--rc-motion-spatial-easing-enter`/`-exit`. An opening element decelerates
+  into place; a closing one accelerates out. There are no matching enter/exit
+  duration tokens; pair `-easing-exit` with an existing `-duration-fast` token
+  instead.
+
+  All three themes map the new tokens: Material pairs them with its
+  standard/emphasized decelerate and accelerate curves, Substrate keeps its one
+  curve as the enter curve and adds a generic accelerate shape for exit
+  (refined further once Substrate gets its own full spatial/effects scale), and
+  `rc-theme-win31` declares all four as `step-end`, matching its zero-motion
+  contract, so an application that loads the shared base tokens alongside
+  `rc-theme-win31` does not inherit the base defaults' real easing curves for
+  these two directions.
+
+- 7c952e2: `rc-theme-material` and `rc-theme-substrate` refine `prefers-reduced-motion:
+reduce` from removing every transition and animation to removing only
+  spatial motion; effects motion (color and opacity) is kept, shortened.
+  Vestibular harm, the reason for the preference, comes from movement across
+  the visual field; a color or opacity change doesn't trigger it, and removing
+  it too was also removing motion that aids comprehension.
+
+  Material's effects duration shortens to 50/70/100&nbsp;ms (from its full
+  150/200/300&nbsp;ms scale); Substrate's to 40/55/70&nbsp;ms, scaled down from
+  its own faster 100/160/240&nbsp;ms base. `rc-theme-win31` needs no change: it
+  already declares every duration at zero unconditionally.
+
+  Several component recipes that bypassed the shared motion scale entirely,
+  referencing a raw duration primitive directly, are rewired to the
+  appropriate effects or spatial token so this refinement actually reaches
+  them: Material's `rc-disclosure`, `rc-list-item`, `rc-bottom-sheet`'s snap
+  duration, `rc-button`'s ripple, and its shared state-layer opacity fade;
+  Substrate's `rc-listbox`, `rc-splitter`, and `rc-disclosure`. Most land on
+  their existing value exactly; `rc-button`'s ripple duration normalizes from
+  450&nbsp;ms to 500&nbsp;ms, the nearest real spatial tier.
+
+- c62d107: Let opt-in native theme styles reach consumer controls inside RC containers while
+  component recipes retain their themed presentation. Apply the same presentation
+  boundary and `data-rc-native="off"` subtree opt-out in Material, Substrate, and
+  Windows 3.1.
+
+  Native controls inside an RC host may now gain theme styling when that host does
+  not provide their appearance. Add `data-rc-native="off"` to content that should
+  keep its own styles, such as a third-party widget.
+
+- 622c5c9: Add independent opt-in `native.css` and CSS-only `css-components.css` entrypoints to the
+  Material, Substrate, and Windows 3.1 themes. Native controls can use the theme presentation
+  without registration, while documented class recipes style common HTML controls and static
+  card, list, chip-group, and disclosure markup without changing behavior.
+
+  Native styles stop at RC controls that own their native children. Add
+  `data-rc-native="off"` to an element to keep native styles off it and its subtree.
+
+- f1ca82d: Add an anchored, non-modal popover package with a Material rich-tooltip recipe. Share native Popover API visibility and fallback behavior across existing popup components.
+- 687a9be: Add shared popup surface tokens: `--rc-popup-background`, `--rc-popup-color`,
+  `--rc-popup-border`, `--rc-popup-radius`, `--rc-popup-shadow`, and
+  `--rc-popup-padding-block`. Menus, adaptive-menu popups, and select and
+  combobox listboxes read them before their own fallbacks. Themes set them at the
+  theme root, so popups rendered inside other shadow roots keep the theme's
+  surface. Select and combobox add `--rc-*-listbox-background` and
+  `--rc-*-listbox-color`.
+
+  Breaking: popup surfaces no longer fall back to `--rc-control-radius`. Set
+  `--rc-popup-radius` (or the per-component radius token) to change popup
+  corners. The Material, Substrate, and Win31 themes no longer set per-component
+  popup surface tokens such as `--rc-menu-radius` or
+  `--rc-adaptive-menu-popup-background`; override the `--rc-popup-*` tokens
+  instead. Material select and combobox listboxes now use the menu container
+  color, Material forced-colors popups gain a border, and Substrate listboxes use
+  the menu shadow and padding. Material retains its two-layer adaptive-menu popup
+  shadow through a component token while other popups continue using the shared
+  shadow.
+
+- c130173: Add pointer and keyboard reordering to `rc-list`.
+
+  Set `reorderable` and give each item a native `<button data-rc-reorder-handle>`. People can drag
+  a handle, and the items it passes shift out of the way while the nearest scroll container
+  scrolls near its edges. On touch and pen, a long press on an item also starts a drag, while
+  movement before activation remains available for scrolling. Or they can focus a handle and use
+  Space, the block-axis arrow keys, Home, End, and Escape. Each step is announced, focus stays on
+  the moved item's handle, and geometry and keys follow the writing mode. `reorderable` implies
+  `ordered`.
+
+  Each committed move fires a cancelable `rc-list-reorder` event with `{ item, from, to }`. Left
+  alone, the list moves the node itself; a framework that renders the items cancels the event and
+  reorders its own data. `reorderMessages` overrides the announcements and the handle hint.
+
+  `rc-common` gains the `ReorderController` behind it and a `LiveAnnouncer` live-region helper.
+  `rc-theme-material` styles the lifted item with the dragged elevation, surface, and state layer,
+  animates the shifting items with standard motion, and presents plain handles as standard icon
+  buttons.
+
+- 6d126fd: Add shared item type tokens: `--rc-item-font-family`, `--rc-item-font-size`,
+  `--rc-item-font-weight`, `--rc-item-line-height`, `--rc-item-letter-spacing`,
+  and `--rc-item-icon-size`. Menu, listbox, and adaptive-menu items read them.
+  Adaptive menu adds `--rc-adaptive-menu-trigger-hover-background`,
+  `--rc-adaptive-menu-trigger-shadow`, and
+  `--rc-adaptive-menu-trigger-active-shadow`, and styles overflowed `rc-button`
+  and `rc-menu-button` rows from its item tokens. Themes declare their menu,
+  adaptive-menu, and item tokens on the theme root, so menus inside other shadow
+  roots match menus in the document. Substrate's adaptive-menu trigger now shows
+  its hover background.
+
+  Breaking: theme menu and adaptive-menu tokens are inherited from the theme root
+  instead of set on each element, so a value set on an ancestor now reaches
+  nested menus. Material sets menu, listbox, and adaptive-menu item type through
+  `--rc-item-*` instead of per-component rules; override those tokens to change
+  item type. Themes no longer style the adaptive-menu trigger through
+  `::part(overflow-trigger)` hover and pressed rules; use the new trigger tokens.
+
+- e23a39c: Add an accessible native input and textarea field wrapper with Material 3 filled and outlined
+  theme treatments, including an explicit provider contract for enhanced native controls.
+- 6b99ced: **Breaking:** replace `LineDisclosureController` with `FoldingActionController`.
+  Pass a caller-owned panel as `target` and render it through a block widget, or pass
+  `{ fromLine, toLine }` to fold source lines. Panel creation and content revision now
+  belong to the plugin. Set `initiallyExpanded: false` to retain the old diagnostic
+  panel default; call `clear()` when document identity changes.
+
+  Folding actions keep source text, form values, and undo history intact. The Markdown
+  plugin adds gutter folds for heading sections, lists, code blocks, block quotes,
+  and GFM tables. The base gutter has a 24px minimum width; Material uses 48px.
+  Folding buttons expose `fold-trigger` and `fold-icon` CSS parts, and
+  `createMarkdownPlugin({ folding: { createTriggerIcon } })` lets consumers choose
+  the Markdown fold icon.
+
+- 3325191: **Breaking:** take `rc-textarea`'s read-only state from the slotted `<textarea readonly>` and
+  remove the `read-only` attribute and its display styling without border or padding. A read-only
+  editor keeps the enabled field appearance, stays focusable and selectable, announces `aria-
+readonly` with the native control's label, and rejects edits. The host reflects `data-readonly`,
+  and `readOnly` is now a getter. The plugin `transform()` hook runs while the textarea is
+  `readonly`.
+
+  `rc-markdown-editor` passes its `read-only` state to a native textarea in its source editor.
+  Material and Substrate fields skip the hover affordance for a read-only control and keep its
+  focus indicator.
+
+  Migration: replace `<rc-textarea read-only>` with `readonly` on the slotted textarea, for
+  example `<rc-textarea><textarea aria-label="Notes" readonly></textarea></rc-textarea>`. Replace
+  `editor.readOnly = value` with `textarea.readOnly = value`. Read-only content that is not a form
+  value belongs in ordinary text or list markup instead.
+
+- 0e2d878: **Breaking:** replace `--rc-textarea-padding` with `--rc-textarea-padding-block` and
+  `--rc-textarea-padding-inline`. The active line highlight bleeds through the inline padding by
+  negating it, which a multi-value shorthand made invalid: inside a Material filled `rc-field`
+  (`0 1rem 0.5rem`) the highlight stopped short of the field's edges in the editor and gutter.
+  `--rc-textarea-padding-inline` is one length applied to both inline sides, so the bleed stays
+  valid and follows RTL and vertical writing modes through logical insets.
+  `--rc-textarea-padding-block` accepts any `padding-block` value.
+
+  Migration: split each `--rc-textarea-padding` declaration. A single length `L` becomes
+  `--rc-textarea-padding-block: L; --rc-textarea-padding-inline: L`. A shorthand
+  `T X B` becomes `--rc-textarea-padding-block: T B; --rc-textarea-padding-inline: X`.
+
+- f5c1a8c: `rc-theme-material` now routes its component motion through the shared
+  spatial/effects token scale consistently. Previously, roughly thirty
+  `transition`/property declarations across combobox, listbox, menu, menu
+  button, menubar, select, range slider, search bar, app bar, textarea,
+  transfer list, toolbar, and splitter carried hardcoded `150ms ease` or
+  `200ms ease` literals instead of the theme's own motion tokens, and the
+  navigation bar/rail's active-item indicator (which resizes to the selected
+  item's box, a spatial change) was themed with a raw Material duration/easing
+  pair outside either scale. Every color/background-color/border-color/
+  box-shadow/opacity transition now uses `--rc-motion-effects-*`, and every
+  transform/scale/translate/inline-size/block-size transition uses
+  `--rc-motion-spatial-*`, splitting any declaration that mixed both kinds of
+  property. `rc-field`'s floating label transition moves its position/size
+  properties (`inset-block-start`, `font-size`) from the effects scale to the
+  spatial scale they actually belong to.
+
+  Five component motion tokens the theme previously left unset are now themed:
+  `--rc-switch-easing`, `--rc-button-state-layer-duration`,
+  `--rc-card-state-layer-duration`, `--rc-card-state-layer-easing`, and
+  `--rc-splitter-snap-duration`. `rc-switch`'s single duration/easing pair (it
+  has no separate spatial/effects knobs) now takes the spatial scale, since its
+  dominant motion, the thumb sliding and resizing, is spatial; this changes its
+  default transition speed under this theme from 150&nbsp;ms to 300&nbsp;ms.
+  `rc-splitter`'s snap-to-point animation moves from its 200&nbsp;ms component
+  default to the same 300&nbsp;ms spatial-fast tier for the same reason.
+
+  The spatial easing curves are now sourced from the semantic aliases added in
+  the last release rather than composed inline from raw control points four
+  times over. Material 3's spec spatial durations are
+  350/500/700&nbsp;ms; this theme's own motion guide finds durations past
+  roughly 400&nbsp;ms read as waiting rather than feedback, so the spatial
+  scale is compressed to 300/400/500&nbsp;ms: a deliberate, recorded departure
+  from the spec numbers, not the spec's `emphasized` curve shape, which is
+  unchanged.
+
+- 40f132d: `rc-theme-material` now declares the Material 3 motion system's seven named
+  easing curves (`--md-sys-motion-easing-standard`, `-emphasized`, and their
+  decelerate/accelerate variants, plus `-linear`) and sixteen named duration
+  bands (`--md-sys-motion-duration-short1` through `-extra-long4`), composed
+  from the control points and millisecond primitives already vendored. Several
+  component recipes were already reaching for these names with an inline
+  fallback (`var(--md-sys-motion-easing-standard, cubic-bezier(0.2, 0, 0, 1))`)
+  that silently won every time because nothing declared the token; those
+  references now resolve for real, and the fallback silently carrying a
+  Material 2 curve (`cubic-bezier(0.4, 0, 0.2, 1)`, in `rc-state-layer`'s
+  transition) is fixed to the correct Material 3 curve. Two more vendored-token
+  gaps of the same shape are fixed alongside: Material's disabled state-layer
+  and container opacity tokens, referenced across a dozen component recipes
+  with no local declaration, and two Substrate token names
+  (`--substrate-border`, `--substrate-radius-medium`) that never matched their
+  real declarations (`--substrate-border-color`, `--substrate-radius-md`) and
+  so always fell back to a hardcoded literal instead of the theme's actual
+  values; `rc-fab-menu`'s Substrate shadow tokens are corrected the same way.
+- 11b8cb9: Theme `rc-select` and `rc-combobox` as `rc-field` control providers: resting, hover, and
+  focus/open chrome resets mirroring the existing `rc-textarea` treatment, so `rc-field`'s own
+  `#field` surface owns the visible border, background, and focus ring instead of the wrapped
+  control rendering its own on top. Standalone (non-wrapped) usage is unaffected; every new rule
+  is scoped to `[data-rc-field-control]`.
+- fb747f6: Declare `rc-base` before each theme's own layers. Components inject their structural
+  light-DOM CSS into `rc-base` at runtime, after the theme has loaded, which made it the last
+  and strongest layer on pages that don't declare their own order, so it could override theme
+  rules. Theme rules now win either way. Apps that declare their own layer order should list
+  `rc-base` before the theme layers.
+
+  Add a fourth theme layer, `rc-theme-*.overrides`, after `.components`. Each theme uses it to
+  keep `rc-adaptive-menu` overflow rows on the menu's item tokens. Theme button and menu-button
+  variants, such as Material's icon-only sizing and filled colors or Win31's bevelled native
+  buttons, no longer restyle an overflowed action as a standalone control. A demoted
+  icon-only `rc-menu-button` keeps its row padding and indicator inset.
+
+- 877a03f: Add a scoped type scale. An element with `data-rc-type-scale` multiplies every Material
+  type size and line height beneath it by `--rc-type-scale`, and derives the RC text
+  tokens built on them (`--rc-item-font-size`, `--rc-font-size`, `--rc-button-font`, and
+  related line heights) again from the scaled values, so lists, buttons, menus, and plain
+  text in the region grow together.
+
+  Marking the theme root itself scales the whole page, for an app-wide text size setting.
+  With `bridge.css` alone, RC text scales from the application's Material type tokens;
+  the application's Material tokens remain unchanged.
+
+### Patch Changes
+
+- 8d6edf2: With `scroll-behavior="hide"`, `rc-app-bar` now publishes read-only geometry onto its scroll
+  target: `--rc-app-bar-block-size`, its measured block size, and
+  `--rc-app-bar-visible-block-size`, the same value or `0px` while hidden. Hiding only translates
+  the bar, so a layout can now give its space back: stack the bar over the scroll container,
+  reserve the block size as the container's block-start padding and scroll padding, and pin
+  sticky content at the visible size minus the block size, since sticky offsets are measured
+  inside that padding. The bar removes both values when it stops hiding, changes
+  target, or disconnects.
+
+  The Material design guide documents this recipe and the compact-height patterns for landscape
+  phones: app bars that hide on scroll, side sheets instead of modal bottom sheets, full-screen
+  task dialogs, media capped by the pane's height, and single-row sticky chips.
+
+- 3d050f1: Keep wrapped chip rows evenly spaced. Readonly chips in an `rc-chip-group`
+  keep the touch-target block size, so expanded rows share the disclosure
+  toggle's pitch. `rc-combobox` and `rc-select` return the chip touch-target
+  overlap tokens as row gap, so interior chip rows no longer collapse onto each
+  other inside a field. Material combobox and select input chips drop their
+  extra block padding to render at the 2rem chip height.
+- 011f3c6: Keep combobox chips clear of their trailing toggle, reset native selects inside
+  `rc-field`, keep controlled carousel accessibility state synchronized, and align
+  Material chips, menus, lists, disclosures, nested editors, and bottom-sheet
+  motion with their MD3 defaults.
+- 3f19f57: Disclosure summaries draw their hover layer only for a pointer that can hover, so a tapped
+  summary no longer stays highlighted on touch screens. The Material theme also spaces disclosure
+  content from its summary.
+- 25375fa: Drop the inner focus ring from `rc-combobox` and `rc-select` when they are
+  composed as `rc-field` controls, since the field's label and active indicator
+  already show focus.
+- 3f8d110: Clear a page-level focus outline from a native input, select, or textarea inside `rc-field`. The
+  field already shows focus, but rc-field's `::slotted()` reset loses to page rules such as a CSS
+  reset's Firefox `:-moz-focusring` outline, which drew a dotted box inside the focused field.
+- cc0205d: Use logical CSS properties so layout follows the reading direction and
+  writing mode: the textarea gutter border and alignment, line-action and
+  diagnostic-message spacing, the markdown editor's block quote and list
+  indents, and block-axis scrolling for listbox, select, combobox, and markdown
+  panes, each keeping its physical declaration as a fallback.
+- 818d193: Clarify that compact-height layouts show one route page at a time and open
+  transient filters or ingredients in full-screen dialogs. Supporting content
+  may form a scrolling column when space permits.
+- 6771ce6: Pin floated Material field labels to the container instead of centering them
+  with the control. Filled fields reserve 8px of block padding, so every floated
+  label sits at the same offset and a taller control grows the field downward;
+  outlined labels now ride the top border for select and combobox controls too. Full-size
+  chips in a filled field keep a 0.25rem gap below the floated label.
+  Select and combobox controls drop their own block padding inside fields, and
+  `rc-textarea` text starts on the input line like a native textarea.
+
+  Add `rc-combobox--dense` and `rc-select--dense`, which render 1.5rem chips so a
+  populated chip field keeps the standard 56px height.
+
+- f5d33fa: Describe which icons mirror in right-to-left layouts, and how an app maps the
+  physical safe-area insets to inline start and end before using them with
+  logical properties.
+- e062f7f: Give the Material typefaces a generic fallback. `--md-ref-typeface-plain`
+  and `--md-ref-typeface-brand` are now `Roboto, system-ui, sans-serif`, so a
+  page without Roboto renders in the system sans-serif instead of the
+  browser's default serif.
+- 622a4f8: Theme popovers and tooltips through the shared token layers. `rc-popover` now
+  reads the shared `--rc-popup-*` surface tokens before its own fallbacks, like
+  menus and listboxes, and `rc-tooltip` takes its default corner from
+  `--rc-radius-sm`. The Material theme sets its popover and tooltip tokens on the
+  theme root, so surfaces inside other shadow roots inherit them, and the
+  Substrate theme adds popover and tooltip styles.
+- 114e38a: `rc-progress`'s determinate fill transition is now themeable through two new
+  CSS custom properties, `--rc-progress-fill-transition-duration` (default
+  `150ms`) and `--rc-progress-fill-transition-easing` (default `ease-out`),
+  replacing a hardcoded `0.15s ease-out` no theme could reach.
+
+  The indeterminate loop's easing changes from `ease-in-out` to `linear`. A
+  loop has no beginning or end to decelerate into or accelerate out of, so an
+  eased loop visibly pulses at each cycle boundary; Material 3 specifies linear
+  easing for indeterminate loops for the same reason.
+
+  `rc-theme-material` and `rc-theme-substrate` map the new duration/easing
+  properties to their effects-fast motion tokens; `rc-theme-win31` already sets
+  `transition: none` on the fill part directly and needs no change.
+
+- 5f1628f: Draw the search bar's keyboard focus ring on the field's edge instead of 2px
+  outside it, where it floated off the pill and crowded the top of the app bar.
+- fef89dc: Move the segmented appearance into the component behind one switch.
+
+  Turning the native fieldset into a segmented control took 27 `--_rc-*`
+  declarations that every theme had to restate, 23 of them byte-identical. Two of
+  those blocks were accessibility recipes rather than taste: the visually hidden
+  legend that keeps the group's accessible name, and the hidden but focusable
+  radio. A theme that got either wrong removed the accessible name or made the
+  control unreachable by keyboard.
+
+  The component now owns the recipe and a theme sets
+  `--rc-segmented-button-appearance: segmented`. Four genuine theme choices become
+  public properties: `--rc-segmented-button-cursor`,
+  `--rc-segmented-button-disabled-cursor`,
+  `--rc-segmented-button-vertical-divider`, and
+  `--rc-segmented-button-selected-icon-display`.
+
+  Unset, the fieldset, legend, and radios keep their browser appearance, as
+  before. The switch is read with a style container query (Chrome 111, Safari 18,
+  Firefox 128); where that is unsupported the recipe does not apply and the
+  control falls back to the same native appearance.
+
+  To migrate a theme, replace its `--_rc-segmented-button-*` block with the single
+  `--rc-segmented-button-appearance: segmented` declaration, plus any of the four
+  public properties whose value differs from the default.
+
+- 77f9c63: Fix three theme gaps where a token fell through to a system color.
+
+  **Substrate had no error color.** `--rc-field-error-color` fell through to `rc-field`'s own
+  default of `Mark`, the system color for the background of highlighted text, which renders as
+  pure yellow and measured 1.07:1 against the field. Validation worked, the message was in the
+  accessibility tree, and it could not be read. Substrate now ships `--substrate-error`, held
+  at hue 25 so it reads as red rather than as a darker shade of the orange primary at hue 48,
+  and the bridge maps it. Both modes clear 7:1.
+
+  Every remaining error fallback of `Mark`, in `rc-field` and in the Material field styles, now
+  falls back to the validation red a user agent uses for an invalid control. The `Mark` usages
+  inside `forced-colors` blocks are unchanged, where a system color is correct.
+
+  **Material never set `--rc-button-text`.** `rc-select`, `rc-combobox`, and `rc-menu-button`
+  read it directly for text drawn over `--rc-button-bg`, which Material sets to the primary
+  fill, so the `ButtonText` fallback gave 3.26:1 in light and 1.70:1 in dark. It now follows
+  `--md-sys-color-on-primary` alongside `--rc-button-color`, giving 6.44:1 and 7.71:1.
+
+  **Substrate referenced three tokens it never declared.** `--substrate-inverse-surface`,
+  `--substrate-inverse-on-surface`, and `--substrate-radius-pill` were used by the bridge and
+  component styles but missing from `defaults.css`, leaving `rc-snackbar` on system colors and
+  the bottom sheet handle on a literal. All three are declared, and a `defaults` test now
+  asserts that every referenced token exists.
+
+- edfd374: Icon slots keep their square while empty. An SVG icon element such as
+  `<iconify-icon>` draws a frame after it mounts, so swapping one in, such as a
+  filter chip's check, no longer collapses the slot and shifts the row for a
+  frame. Icon-font glyphs already fill 1em and render the same.
+- 22c23df: Ship `DESIGN.md`, a Material 3 composition guide for AI coding agents covering
+  component roles, adaptive layouts by window size class, dialogs, sheets, lists,
+  navigation and feedback, with the baseline token values as front matter. The
+  guide is exported as `@rcarls/rc-theme-material/DESIGN.md` so Plug'n'Play
+  consumers can resolve it.
+- 790c50d: Full-screen dialogs now use the Material 3 `surface` role, matching their top app bar, instead
+  of the basic dialog's `surface-container-high`. Apps no longer need to set
+  `--rc-dialog-fullscreen-background` themselves.
+- 1aff823: Document icon font wiring as one copy-pasteable rule.
+
+  The theme sizes icon markers but sets no `font-family`, so a marker without one
+  renders as its literal text. That was documented per component, which meant
+  adopting a component could reintroduce the problem one marker at a time. The
+  README now lists every marker in the catalog in a single rule, and names the
+  three that carry no sizing from the theme either.
+
+- 3a5d979: Restore a multiline control-provider field's top spacing so its label sits as
+  far below the field's top edge as a single-line field's label does. A
+  single-line field gets that space for free from centering content within a
+  taller field surface; a multiline control-provider's content fills the
+  surface's whole height instead, so the label sat flush against the top edge
+  with no room above it.
+- 4457e71: Fix two token generator defects that produced plausible but wrong output.
+
+  A font shorthand read as a single number. `var(--weight, 500) var(--size, 1rem) / var(--lh)
+var(--family)` both starts and ends with `var(`, and the anchored pattern's fallback group is
+  greedy, so it matched as one `var(--weight)` whose fallback was the rest of the declaration and
+  resolved to `500`. The export carried `card/title-font` and `card/subtitle-font` as floats that
+  were really a collapsed shorthand. A value now counts as an alias only when its opening `var(`
+  closes at the end of the string.
+
+  A mix weight written as a `calc` only worked by accident. Material writes its state layers as
+  `color-mix(in srgb, var(--color) calc(var(--opacity, 0.08) * 100%), transparent)`. The old code
+  pattern-matched a trailing percentage off the operand, leaving a malformed remainder that
+  happened to resolve through the greedy match above. Mix operands are now split at parenthesis
+  depth zero and the weight resolves through the same resolver.
+
 ## 0.6.0
 
 ### Minor Changes