Feature Library

Comments and tasks on anything

1.08 CPU ms
A still of the Comments and tasks on anything demo
Still
The live demo starts when it’s in view.Click a pin or a card · click the sketch to comment on a spot · type @ to mention · drag cards between columns (Alt + arrows)

Comment threads pinned to items or to spots, with replies, @mentions (the longest name wins), edit, resolve and reopen; task cards with a status, an assignee…

What it costs a frame

1.08 ms
GPU
not used
CPU, median
1.08 ms
CPU, 95th pct
2.04 ms
Draw calls
0
Weight
Moderate

Measured 7 November 2026 on 13th Gen Intel(R) Core(TM) i9-13900H, Chrome 156, 1920×1080 at 1×. 600 frames × 3 rounds, median kept. What ran: Measured exercising itself: every frame makes one change through the store (a reply, resolve or reopen, a card moved a column, the clock moved on) and the page redraws its pins, its kanban and the open thread, as it would for a change arriving from someone else. Phones: tiers are being measured next.

On every machine it was measured on
MachineGPU msCPU msCPU p95
unknown GPU · 13th Gen Intel(R) Core(TM) i9-13900Hreference · measuring toolnot timed1.082.04
apple · Apple A19 Proin a browser tab · 16 November 2026not timed1.082.08
Intel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258Vin a browser tab · 15 November 2026not timed2.093.81

Bars against one 16.7 ms frame. A browser-tab run is timed in a visible tab without the tool’s scripted input, so read it as close, not exact.

What it needs

Renders with
DOM and CSSPlain DOM and CSS: every current browser.
Your browser
Runs hereNo WebGPU needed
Depends on
NothingNo other packages

What it’s for

  1. Review comments on designs, boards and documents
  2. Pins on a map, an image or a canvas
  3. Task cards and a light kanban
  4. Feedback threads in an admin tool
  5. Collaborative apps on Yjs or a server

Pitfalls, in brief

  1. A whole name typed after @ is the one put in. suggestPeople sorts an exact name first, so Enter mentions “Sam”, not “Sam Hill”; keep that if you rank people yourself (by team or recent use), or Enter swaps a whole name for a longer one that starts the same way (the owner’s Spacious app had that bug in a formula field’s completions).
  2. Import comments.base.css, then comments.css (or your own look instead).
  3. Mentions are found by the names you pass (people): a name not in the list is plain text.
  4. The longest name wins: with “Bo” and “Bo Lund” known, “@Bo Lund” mentions only Bo Lund.
  5. Store a thread as one value (the functions write the whole thread): two people replying at once on a last-write-wins store can lose a reply.
5 more in brief
  1. Item pins are a share of the item’s size, so they follow a resize; page pins are in whatever frame you choose.
  2. Due dates are YYYY-MM-DD and compared in UTC with todayIso().
  3. Times in words go stale: redraw them when nextChange() says (the thread panel does).
  4. Status signs (○ ◐ ■ ●) carry the status besides colour: keep them, or a word, wherever the colour is shown.
  5. The thread panel takes Esc for itself: an open suggestion list closes first, an edit is cancelled next, then the panel asks to close (onClose).
10 pitfalls in full, the hook-up guide, the module source and its tests come with the part.

Where it comes from

From SpaciousPro. Fully custom code.

WAI-ARIA Authoring Practices Guide (W3C): The combobox pattern (a list of suggestions with aria-activedescendant) for @mentions in the reply box. Written here from scratch.

commentsthreadsmentionstaskskanbanchecklistrelative timeIntlcollaborationadaptercomboboxaccessibilitydomno dependencies

Near it in the frame