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

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

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

Visibility: public

Requested revision: 8641337f80ec4434a7d69b7984a6793e375892b0

Requested commit: 8641337f80ec4434a7d69b7984a6793e375892b0

Commit: 8641337f80ec4434a7d69b7984a6793e375892b0

Tree: 5397fd0519c6ab1ce3f807b9fedc86471639d804

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

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

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