The live demo starts when it’s in view.Open a receipt · answer the conflict · fix the missing date · switch the shared folder on · bring in two more
Where everything a person must look at waits, with the reason in plain words and what can be done.
What it costs a frame
CPU
<0.01 ms
02468101216.7 ms
GPU
not used
CPU, median
<0.01 ms
CPU, 95th pct
1.30 ms
Draw calls
0
Weight
Light
Measured 13 November 2026 on RTX 4060 Laptop, 13th Gen Intel(R) Core(TM) i9-13900H, Chrome 157, 1920×1080 at 1×. 600 frames × 3 rounds, median kept (rounds ranged CPU <0.01–<0.01 ms). What ran: Measured with the demo working through its own queue: every 12 frames it opens the next item (the detail is rebuilt: notes, values, history, and for the conflict the side-by-side table and its choices) and flips "Only differences" on the conflict. Nothing runs between those steps. Phones: tiers are being measured next.
apple · Apple A19 Proin a browser tab · 16 November 2026
not timed
<0.01
3.94
Intel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258Vin a browser tab · 15 November 2026
not timed
<0.01
1.72
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
Imports, uploads and scanned documents a person must check
The same record arriving twice with other values
A moderation or approval queue
Sync conflicts shown field by field
Any job that waits instead of guessing
Pitfalls, in brief
The app owns the items: onAction changes your data, then you call update(items).
A choice is final in the app’s eyes: Keep, Replace and Add run at once (as in the source).
Replace needs the old row in place (conflict.row).
A conflict waits while other answers write.
Compare only columns that carry read values (conflict.compare).
4 more in brief
Values are compared after normalising (empty is null, numbers to two decimals, text trimmed, midnight times as dates).
validate runs before a fix is sent; the rules must still run in onAction (duplicates, totals), because fixed values can make a conflict.
Import review-queue.base.css, then review-queue.css (or your own look).
The narrow view is a container query on the queue’s own width (40em), not the window’s: give its host a height, and the panes scroll inside it.
9 pitfalls in full, the hook-up guide, the module source and its tests come with the part.
Where it comes from
From My other apps. Fully custom code.
WAI-ARIA Authoring Practices Guide (W3C): the Tabs pattern for the views (arrow keys, one Tab stop), the Switch pattern for “Only differences”, and announcements through a polite live region
reviewqueueinboxtriageconflictdiffcompareduplicatesside by sideonly differenceskeep replace addfix valuesmanual reviewingestmaster detailtabsswitchkeyboardlive regionaccessibilityrtldomcsstested
A small appearance system: colour presets as CSS variables (light, dark, two high-contrast, two accent looks), a “Match system” choice that follows the…