# perf\(web\): keep timeline minimap animations off the main thread · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/fe8b2ed9b65591bde6939644a02711564705f20f)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: fe8b2ed9b65591bde6939644a02711564705f20f

Requested commit: fe8b2ed9b65591bde6939644a02711564705f20f

Commit: fe8b2ed9b65591bde6939644a02711564705f20f

Tree: a3dcfad93ac0d4da9ef76bd1b485bddcff7b8f16

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
perf(web): keep timeline minimap animations off the main thread

A renderer performance trace showed the minimap strips as a standing
source of main-thread frame work: each strip transitioned
background-color (paint) and width (layout), and both fire constantly —
scrolling or streaming flips a band of in-view states at once, and the
hover fisheye animates several widths at a time — so any interaction
kept a 60fps style/layout/paint pipeline running.

The strip now animates only compositor-friendly properties: width tiers
are scale-x on a fixed-width box, and the in-view highlight is a bright
overlay faded with opacity. The scroll handler also skips no-op
data-in-view attribute writes, which previously re-dirtied style state
for every strip on every scroll tick.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

```

## Parents

- [911d143bd8a58a943e8c0dbcd12d4a763e954b7f](https://git.cafe/pingdotgg/t3code/commit/911d143bd8a58a943e8c0dbcd12d4a763e954b7f?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/fe8b2ed9b65591bde6939644a02711564705f20f?format=markdown)