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

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

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

Visibility: public

Requested revision: 7ef8c3625adcc8a4dd8fa7e16ec6fdcc72b7c480

Requested commit: 7ef8c3625adcc8a4dd8fa7e16ec6fdcc72b7c480

Commit: 7ef8c3625adcc8a4dd8fa7e16ec6fdcc72b7c480

Tree: e1802d34ec9c4d8515a6a0de988071862f121109

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

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

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