Duolith docs

0108. Sixteen more kit parts, and the expanded and sorted attributes

  • Status: Accepted (Mik, 16 Nov 2026)
  • Date: 2026-11-15
  • Decided by: domain E implementer (internal only)
  • Planning item: wave 5, new kit parts

Decision

The kit gains Accordion, ActionSheet, Banner, ChipInput, Combobox, DataTable (sorting), Fab, FileInput, Pagination, Pager (a carousel of pages, which also pages on a swipe), ProgressRing and Rating (promoted from the gallery's own component), and the gesture parts SwipeRow, PullToRefresh, Drawer and DateRangePicker (decision 0121). Each has a spec in spec/kit/ with its own look tokens (decision 0103), works on the web and on native from the same file, and is driven in a browser twice: on the web by packages/kit/test/more-parts-in-browser.test.ts, and on native, through Lynx for Web, by packages/engine/test/native-kit-in-browser.test.ts. examples/kit/pages/more.duo shows all sixteen.

  • **expanded**, a common attribute (a language change): expanded={open} says whether what an element shows and hides is open. It is aria-expanded on the web and "expanded" or "collapsed" in the accessibility value on native. Accordion's headings use it.
  • FileInput does not pick files itself: its onPick is where the page calls the media-picker effect, by its contract, and adds what comes back to files. The kit never depends on an effect's implementation.
  • Rating's arrow keys come from the radio-group role, as RadioGroup's do, because on:key on a view is never heard on a phone (E0207).
  • **sorted**, a common attribute (a language change): sorted="ascending" | "descending" | "none" on a column header. It is aria-sort on the web and "sorted ascending" or "sorted descending" in the accessibility value on native (nothing for "none"). DataTable's headers use it.
  • DataTable is a table with cells (two new roles), not a grid: it has no cell-to-cell arrow keys, so grid promised keys it did not have. Its sort buttons are named "Sort by <column>".
  • Combobox follows the WAI-ARIA combobox pattern on the web: its field is role="combobox" with aria-expanded and aria-controls, and its suggestions are a listbox overlay that does not take focus from the field. ArrowDown and ArrowUp move into the options (an <input> now hears on:key, and the overlay sends them on), Escape closes them and leaves focus in the field, and choosing one returns focus to it. On a phone the field hears no keys, so the suggestions are pressed, which is what VoiceOver and TalkBack offer anyway.
  • **On native, a 0 flex basis is written as 0%.** flex: 1 1 0 in a column whose height is not set collapsed to nothing in Lynx, which has no min-height: auto; 0% of an indefinite height resolves to the content's size, as a browser draws it. emit-native does this for every style block, so the page's flex: 1 1 0 columns stay as written.

Consequences

spec/language/elements.yaml lists expanded and sorted, the table and cell roles and on:key on <input>; the grammars and references are generated from it. Nothing this decision named is left unbuilt.