Table
Rows of data in a recessed screen well. A real <table> with a real <caption>, compound parts for a table you lay out yourself, and a data mode for one you don't: given columns and rows it sorts (LED pips and aria-sort), selects (Checkbox, with a select-all that can read 'some'), filters, keeps its header at the top, windows thousands of rows, and shows loading and empty rows. Rows that move slide to their new place.
Feel A readout ruled into rows: the numbers line up, the rules stay quiet, and a sorted column's pip lights up.
Preview
| Guitar DI | 3 | 12:33 | |
|---|---|---|---|
| Kick close | 4 | 03:32 | |
| Overheads | 5 | 05:48 | |
| Room tone | 1 | 02:41 | |
| Vocal pass | 2 | 01:07 |
Or let the agent fetch it: get_component("table") on the Echo MCP server.
Installation
First time? Run npx echo-ui-cli init once — it sets the project up, and add refuses to run before it.
At a glance
- Version
- 0.3.0
- Weight
- 4.0 KB · 40.6 KB with what it imports · 2.3 KB of CSS (minified and gzipped; React not counted)
- Needs
- gsap, checkbox (Echo, brought with it)
- Keyboard
- The table sits in a scroll region named by the caption and reachable by Tab, so a wide or tall table can be scrolled from the keyboard.
- A sortable column's header is a button: Enter or Space sorts by it, and again reverses it. The sorted column carries
aria-sort, and the new sort is said aloud ("Sorted by Length, descending"). onRowPressputs a real button in the row's label cell: the keyboard presses the row there, and a click anywhere else on the row does too.
- Reduced motion
- Rows take their new places at once and new rows appear without fading; a pressed row doesn't dip, and loading rows don't pulse.
- Sound
- The select click when a header sorts, a tap when a row is pressed, and the Checkbox's own click, inside a SoundProvider.
Usage
import { Table } from "@/echo/table";
<Table
caption="Recent takes"
columns={[
{ key: "take", header: "Take", rowHeader: true, sortable: true },
{ key: "length", header: "Length", numeric: true, sortable: true },
]}
rows={takes}
getRowId={(take) => take.id}
selectable
/>Composition
Table (data: columns + rows)
Table (compound)
Table.Head
Table.Row
Table.HeaderCell
Table.Body
Table.Row
Table.HeaderCell
Table.CellExamples
Sort, select and filter
Give it columns and rows. Pressing a sortable header sorts by it; `selectable` adds the checkboxes; `filter` comes from your own search Field.
const columns = [
{ key: "take", header: "Take", rowHeader: true, sortable: true },
{ key: "input", header: "Input", sortable: true },
{ key: "length", header: "Length", numeric: true, sortable: true },
];
<>
<Field label="Search takes" type="search" value={query} onValueChange={setQuery} />
<Table
caption="Recent takes"
columns={columns}
rows={takes}
getRowId={(take) => take.id}
selectable
filter={query}
defaultSort={{ column: "take", direction: "ascending" }}
/>
</>Thousands of rows
With a height and `virtual`, only the rows in view are drawn. The header stays at the top.
<Table caption="Events" columns={columns} rows={events} getRowId={(e) => e.id} height={480} virtual size="sm" />Loading and empty
Placeholder rows while the data is on its way; your own words when there's none.
<Table caption="Invoices" columns={columns} rows={invoices ?? []} getRowId={(i) => i.id} loading={!invoices} empty="No invoices yet." />Row actions, and a row that opens
`rowActions` ends each row; `onRowPress` makes the row a press, through a real button in its label cell.
<Table caption="Projects" columns={columns} rows={projects} getRowId={(p) => p.id} onRowPress={(p) => open(p.id)} rowActions={(p) => <HardwareButton size="sm" variant="ghost" onClick={() => archive(p.id)}>Archive</HardwareButton>} />A readout you lay out yourself
Numeric cells align to the end (the right, in left-to-right text) and use tabular figures.
<Table caption="Recent takes">
<Table.Head>
<Table.Row>
<Table.HeaderCell>Take</Table.HeaderCell>
<Table.HeaderCell align="end">Length</Table.HeaderCell>
</Table.Row>
</Table.Head>
<Table.Body>
<Table.Row>
<Table.Cell>Room tone</Table.Cell>
<Table.Cell numeric>02:41</Table.Cell>
</Table.Row>
</Table.Body>
</Table>Caption carried by the surrounding heading
Hide it visually; it still names the table and its scroll region.
<Table caption="Recent takes" hideCaption>…</Table>Accessibility
- A real
<table>with a requiredcaption.hideCaptionhides it visually but keeps it as the table's name. - The table sits in a scroll region named by the caption and reachable by Tab, so a wide or tall table can be scrolled from the keyboard.
- A sortable column's header is a button: Enter or Space sorts by it, and again reverses it. The sorted column carries
aria-sort, and the new sort is said aloud ("Sorted by Length, descending"). - Every row's Checkbox is named by its row ("Select Room tone"); the header's selects every row shown, and reads as mixed when only some are.
- What a filter leaves is said aloud ("3 of 12 rows"), and so is loading; a loading table is
aria-busy. - With
virtual, the table carriesaria-rowcountand each drawn row itsaria-rowindex, so position is announced out of the whole. onRowPressputs a real button in the row's label cell: the keyboard presses the row there, and a click anywhere else on the row does too.- Use
rowHeader(orscope="row"on a leading HeaderCell) so each row is announced by its label.
Tested against WCAG 2.2 AA on every release:
axe— No axe violations, in the component's own gallery and on its page.keyboard— Every action is reachable and operable from the keyboard alone.focus-visible— Focus is visible on every focusable part, in normal and forced-colors mode.forced-colors— State stays visible when the look's colours are replaced by the system's.target-size— Every target's real hit area is at least 24×24px, at every density.reflow— Content reflows into 320px and survives a doubled text size.
Not covered: screen-reader: not yet verified by a person. Everything above is a machine check; a person has not yet driven this component with a screen reader.
Motion & sound
- Motion tokens
travel,summon- Reduced motion
- Rows take their new places at once and new rows appear without fading; a pressed row doesn't dip, and loading rows don't pulse.
- Sound
- The select click when a header sorts, a tap when a row is pressed, and the Checkbox's own click, inside a SoundProvider.
Props
| Prop | Type | Default |
|---|---|---|
caption requiredWhat the table is. Required; names both the table and its scroll region. | string | |
hideCaptionHide the caption visually. It still names the table. | boolean | false |
stripedFaint bands on alternate rows. For wide tables; the rules already separate rows. | boolean | false |
sizeRow height from the control scale: sm 32px for dense screens, md 44px, lg 60px. Default md with columns; content height without. | "sm" | "md" | "lg" | |
columnsData mode: { key, header, value?, cell?, sortable?, align?, numeric?, rowHeader?, filterable? } for each column. With rows, Table draws the head and body itself. | TableColumn[] | |
rowsData mode: the rows, in any shape; columns read them. | unknown[] | |
getRowIdData mode: a stable id for a row. Selection is kept by it. | function | |
sortThe sort, controlled: { column, direction }, or null for none. | object | |
defaultSortThe sort to start with, uncontrolled. | object | |
onSortChangeCalled with the new sort when a header is pressed. | function | |
selectableA Checkbox on every row, and one in the header that selects every row shown (and reads 'some' when some are). | boolean | false |
selectedSelected row ids, controlled. | string[] | |
defaultSelectedSelected row ids to start with, uncontrolled. | string[] | |
onSelectedChangeCalled with every selected row id. | function | |
filterA query: rows with a value containing it stay. Set it from your own search Field. | string | |
filterRowsYour own filter, instead of 'any value contains the query'. | function | |
heightThe table's own height (a number is pixels). It scrolls inside, and its header stays at the top. | number | string | |
virtualDraw only the rows in view, for thousands of rows. Needs height; each row is one line at the size's height. | boolean | false |
loadingRows are on their way: placeholder rows, and a busy table. | boolean | false |
emptyWhat an empty table says. A filtered one says what matched nothing. | ReactNode | |
rowActionsThe end of each row: (row) => … its actions (ghost HardwareButtons, a Menu). | function | |
onRowPressMakes each row a press: its label cell becomes a button, and a click anywhere else on the row presses it. | function |
Anti-patterns
- Never use a table for layout. These are real table semantics, and a screen reader will announce rows and columns for something that has neither.
- Never drop the caption to save space: use hideCaption. An uncaptioned table is an unlabelled grid of numbers to anyone not looking at it, and its scroll region loses its name too.
- Never remove the tabIndex from the scroll container. An overflow region that cannot take focus is unreachable by keyboard; a mouse hides the bug completely.
- Never mix numeric and text cells in one column and set numeric on only some: the column stops aligning, which is the entire reason to mark numbers at all.
- Never sort or filter the rows yourself and in Table at once: give Table all the rows, and let
sortandfiltersay how they show. - Never set
virtualwithoutheight: with nothing to scroll, there's no window, and every row is drawn anyway. - Never give a row press a click handler on the row alone:
onRowPressputs the button in the label cell, which is what the keyboard reaches.
Changelog
- The drawn device (
echo-ui-core,echo-ui-cli, every component that draws its own material). A seed's newrendersetting ismolded(Echo as it has always been: plastic lit by one key light) ordrawn: the same parts drawn in the ink, the way a spec sheet draws a key. Every part is outlined at one weight (--echo-line,--echo-line-width), hollow on the body; a raised part stands on a hard ink edge as deep as it rises and travels down it when pressed; a recess is an outline drawn inside; something floating stands on a deeper edge. There's no light, so no gloss, no soft shadow and no glow: what a molded device lights (an LED, the rail, a readout, the focus ring, a fader's knob, a radio's pip) is solid ink, and a low-emphasis action is its label underlined. In black and white (the accent the ink) "on" is solid ink and what's drawn on it inverts: a switch's thumb turns paper, a fader's knob is knocked out with a paper ring. The primary key is the paper key that stands highest, on an ink edge twice as deep as a neutral one's, the way a spec sheet draws its CTA. The accent stays the seed's own colour as a flat fill for what's on (a chosen segment, a checked box, a slider's travel, a switch that's on), so an acid highlighter is acid, not the olive a molded device holds it to; what's drawn on it is the ink, or the body when the accent is too deep for the ink. Pressing, travel, sound, what each material is for and every contrast guarantee are unchanged.npx echo-ui-cli style set render drawnturns it on; a style sets it in its seed; the published style and config schemas describe it, andDESIGN.mdsays how a drawn device builds. A molded device renders exactly as before: every line is 0px wide there, and each drawn value a component reads (--echo-drawn-fill,-on-fill,-ink,-rule,-glass,-hollow,-decoration) isinitial, so it falls back to what the component always drew. HardwareButton's bed is the one new hand-tuned shadow: a drawn key stands on its own edge instead of being drawn in a recess. - Every item needs
echo-ui-core0.3.0 (all components). The drawn device, readability past AA and the design tests live in core, and the components that use them are built against it, so each item now declaresecho-ui-core >=0.3.0 <0.4.0. Update core with the items:npm install echo-ui-core@^0.3.0(or your package manager's), thennpx echo-ui-cli update. An item whose files didn't change is the same code under a new version; the 0.2.0 files stay published. - The light device (
echo-ui-core,echo-ui-cli). Echo can be light: a pale chassis makes a device molded in light plastic, like a white calculator or a cream radio, and a dark one makes the device Echo has always been. There's no setting and no mode to switch; the chassis decides (devicePolarity, andvalues.polarityon the theme). On a light device the page is light: its ground, the well, is the body barely set in. Caps get their own ladder, a step lighter than the body with a lit rim that stops short of white, so they keep their bevel; undersides and seams are shaded darker; dim text moves toward the ground by the same step as on a dark device, and reads about 6:1 on it. Screens are paper glass printed in ink, because a glow on a pale body is a smudge. What's lit (an LED, the current rail) is still the accent, held to 3:1 on every ground, so on is brighter than off; the text it prints (a readout, a count, a current tab) and the focus ring are the accent's ink, a step deeper and held to AA, in the newaccent-inkrole. The primary cap is the same cap as a dark device's, the accent with a light label: its label is the newprimary-cap-inkrole, and progress cells, loader dots and a meter's fill, the same plastic, read 3:1 on the page. A neutral cap or a slider that fills with it under its own dark label fills with the newpour-*roles, the accent's pale stops. Shadows are drawn at half their weight, in a deep colour of the body's own hue (--echo-cast-ink) instead of black. Every guarantee holds as it does on a dark device, and the contrast sweep now runs on light bodies too. A dark seed makes exactly the theme it did before, and the new roles equal the ones they stand for there. The components that mixed a recess toward black, painted paper in the text colour or lit a pillow of light with it read the theme's new--echo-shade-ink,--echo-paper-stockand--echo-paper-inkinstead, with the old value as the fallback, and a reflective screen reads--echo-screen-*; the components that print a lit label read--echo-primary-cap-inkand--echo-accent-inkthe same way; every rail is drawn in the glow, and every focus ring, theringrecipes included, in the ink.style usewears a light style now, andstyle checksays which device a style makes. A dark screen tint on a light body is still refused: one text colour can't serve both, and the theme says so. - Table sorts, selects, filters and windows its rows (
echo-table). Give itcolumnsandrows(andgetRowId) and it draws the head and body itself: a sortable column's header is a button whose LED pips light the direction, witharia-sort;selectableadds a Checkbox to every row and a select-all that reads "some";filteris a query from your own search Field;sizesets the row height from the control scale; a table with its ownheightkeeps its header at the top, and withvirtualdraws only the rows in view, so two thousand rows cost a screenful.loadingandemptyrows,rowActions, andonRowPress(a real button in the label cell) round it out. Sort and selection work controlled or not. Rows that move slide to their new place, new ones fade in, and a pressed row gives; under reduced motion, none of them move. The sort, a filter's count and loading are said aloud. A table laid out by hand works as before. - Comments only, no behaviour change. Comments in the component source used to cite documents, milestones and ticket numbers from Echo's own planning, none of which exist in your project. The citations are gone and the sentences around them stay. Where a comment was only a citation, it now says what it meant. Three development warnings (
HardwareButton'sengraved/captionchecks andStatusDot's missing-label check) also dropped the ticket code at the end of the message.echo-ui diffwill show changes in most items; none of them are to code. - An item's version is now a function of declared data, not of how the changelog is formatted. The version an item ships under is published once and never rewritten, and it used to be inferred from prose: a regex for a bolded "Breaking" run across the whole unreleased section, and attribution by "does a bullet mention this name in backticks". One breaking entry therefore moved every item that changed that cycle, and an entry explaining that "
MenuandSheetare unchanged here" filed itself as a change to Menu and Sheet — which it really had. - The agent brief says Echo has not shipped.
llms.txtand the MCP server's instructions led withnpx echo-ui-cli init, and that name on npm is a reserved stub with no executable — so a model following the brief wrote an install step that fails with npx's own error. The brief now opens with the caveat, and the docs carry it on every surface that shows a command. One switch (CLI_RELEASED) silences all of them at launch, and a test refuses to let one move without the others. Affectsall componentsonly in what the brief says about installing them; no item's props, CSS or rendered semantics change. - Echo's home is
echo-ui.com. The registry, the docs and the packages all move to it fromecho.nawwara.studio. Nothing was published under the old host, so noecho.jsonanywhere points at it and there is nothing to migrate — this is the last release where that is true. - Weights, line heights, letter-spacing, z-index, border widths and icon sizes come from the theme scales in
all components, with the old value as a fallback, so components keep working withecho-ui-core@0.0.1. Strays moved to the nearest step: most by under a pixel; HardwareButton icons are 14/16/20px (were 15/17/19). - A light device's recesses keep the body's hue in Chromium (
echo-ui-core, BUG-166). Chromium drops the hue of a colour under 0.02 chroma when it mixes in oklch, and draws the mix at hue 0, a rose. A light device's plastic is that grey, so on a lilac body every field, track and rail was pink. A mix made only of greys is made in oklab now, which has no hue to lose; a mix with an accent in it stays in oklch. On a dark device nothing you can see changes. - On a phone, a tapped part no longer stays lit (BUG-143). A phone leaves what you tapped under
:hoveruntil the next tap, so a table row stayed shaded and a trigger stayed lit after the finger lifted. Hover styles now apply only where there's a pointer that can hover (@media (hover: hover)), in all 23 components that had one. Checked, active and focus styles that shared a rule with them still apply everywhere. - Content now reflows into a 320px screen (400% zoom) and survives a doubled browser text size (WCAG 1.4.10, 1.4.4), across
all components.Select's 180px floor,NumberField's readout,SegmentedandStepsas flex items,EmptyState's grid columns, andAvatar's fixed-pixel disc all gave way;Panelcounts its padding inside a width you set (box-sizing: border-box), so a<Panel style={{ width: 220 }}>is now 220px wide overall rather than 260px.