Feature Library
0.28 GPU · 0.48 CPU ms
A still of the Jelly marks demo
Still
The live demo starts when it’s in view.Drag a session to another day · press one to squash it · focus one and press Enter, then the arrows, to carry it

Refracting gelatine boxes laid on a page’s own elements.

What it costs a frame

0.28 ms
0.48 ms
GPU
0.28 ms
CPU, median
0.48 ms
CPU, 95th pct
0.89 ms
Draw calls
0
Weight
Light

Measured 15 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 GPU 0.28–0.54, CPU 0.30–0.48 ms). What ran: Measured with the demo running itself from its first frame: every 0.8 s it shakes every mark, moves a session a day along and back (its jelly slides in the month and its brick between the weekday wells), or presses one, while the clashing sessions tremble throughout. The marks are driven from the demo’s update(), so CPU time is the springs, the reads of the moved cells and the riding labels, and GPU time the two passes (floor with trays, shadows and caustics, then the refracting marks at 4× multisampling), from their timestamp queries. Phones: tiers are being measured next.

On every machine it was measured on
MachineGPU msCPU msCPU p95
RTX 4060 Laptop · 13th Gen Intel(R) Core(TM) i9-13900Hreference · measuring tool0.280.480.89
apple · Apple A19 Proin a browser tab · 16 November 20266.820.921.32
Intel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258Vin a browser tab · 15 November 20262.230.450.86

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.

How steadily it runs on Intel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258V · in a browser tab

Typical frame ?
16.69 ms
1% low ?
52 fps
Varies by ?
±0.50 ms
All metricsIntel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258V · in a browser tab
p50p95p9916.02 ms18.80 ms +
How long each frame took. Most frames sit in the tall bars; a long tail to the right is hitching.

Frames run on a 60 Hz timer (a page demo), so most frames take about one tick, 16.7 ms: the spread around it is what matters.

Frames

Median (p50) ?
16.69 ms
p95 ?
17.52 ms
p99 ?
18.07 ms
Slowest ?
22.38 ms
Mean ?
16.73 ms
Standard deviation ?
0.50 ms
1% low ?
52 fps
0.1% low ?
45 fps
Hitches ?
0 of 600
Over budget ?
0 of 600

Main thread

Long tasks ?
0
Long frames ?
0
Event-loop delay ?
0.1 / 1.4 / 3.0 ms

Input

No input during this run. A browser-tab run plays none.

Memory

JavaScript heap ?
111 → 111 MB
Growth ?
-0.06 MB

What it needs

Renders with
WebGPUNeeds WebGPU: current Chrome and Edge, Safari 26+, Firefox 141+ on Windows.
Your browser
Checking…Looking for WebGPU
Depends on
NothingNo other packages

What it’s for

  1. Calendars and planners whose bookings feel like things you can pick up
  2. Bar, column and stacked charts whose marks answer the hand
  3. Showing conflicts by motion as well as words: a clash trembles until it is moved
  4. Kanban boards and trays of items moved between cells
  5. Playful dashboards that stay plain DOM underneath

Pitfalls, in brief

  1. Give marked elements and trays no background of their own: the canvas behind the host draws them.
  2. The host becomes a stacking context (isolation: isolate) and the canvas sits at z-index −1 inside it.
  3. Marks are read from the DOM: their boxes, their border radius and the computed --jm-color.
  4. Each marked element rides on its jelly: the module sets its CSS translate (and opacity while it pops in) every frame.
  5. Ids are data-jm-mark’s value and must be unique in the host: a mark keeps its jelly while its id stays, so a list drawn again from scratch still slides.
5 more in brief
  1. The first scan and every resize land at once.
  2. Trembling is information here (a clash), and reduced motion stills it: say the same thing in words or a sign as well (the demo’s ▲ and its labels).
  3. Colours can be any CSS colour.
  4. Without WebGPU, or with the renderer set to dom, the marks are CSS blobs driven by the same springs: no refraction, caustics or light.
  5. A drag is yours to write (the module has hold and release): it knows where a jelly is, not what a drop means.
10 pitfalls in full, the hook-up guide, the module source and its tests come with the part.

Where it comes from

From HaTac, and in the planner showcase. Fully custom code.

Mark Jarzynski and Marc Olano, Hash Functions for GPU Rendering (JCGT 2020): The PCG hash behind every random number: the phases, the shakes, the sprinkles and the bubbles, the same in TypeScript and WGSL.

Inigo Quilez, 2D distance functions: The rounded-box distance the trays and shadows are cut with (sdRound), after his published formula.

WAI-ARIA Authoring Practices Guide (W3C): The demo’s month and chart are each one Tab stop with the arrow keys moving inside; a session is picked up and put down with Enter, and moves are said in a polite live region.

jellygelatinerefractioncausticsspringssquash and stretchcalendarmonth viewchartsdrag and dropraw webgpuwgsldom + gpushift lensdesign tokensreduced motionseededkeyboardno dependencies

Near it in the frame