Files
gui/apps/kitchen-sink/tests/ReanimatedEmitterLatch.test.tsx
zeekayandHanzo Dev 69c6e860d7 transplant onto tamagui v2.6.0, brand as a re-runnable transform
This repo could never sync. There was NO merge-base with tamagui — 372 commits
here against 15,791 there, unrelated histories — because it began as a
copy-paste rebrand with a flattened layout. Every "sync" since was a hand
re-application that drifted, which is why the tree sat on 7.3.1 while upstream
shipped fixes we then rediscovered by hand.

This commit's PARENT IS TAMAGUI. A future sync is `git merge tama/main` then
`node scripts/rebrand.mjs` — a real merge, because the history is now shared.

174 packages: 166 upstream, our 8 restored (chrome, shell, telemetry, recipes,
get, font-geist-{sans,mono}, @hanzo/booker), bento-get gained. 170/170 build.

Our patches to files UPSTREAM ALSO OWNS are carried, which the package-level
delta missed and which was where the value actually was:
  - useMedia's server snapshot (`initState ?? getMedia()`). Upstream still
    returns undefined there, so every Tamagui Dialog kills a prerender — the
    exact crash hanzo.app spent a day on.
  - data-slot on web host nodes, absent upstream entirely.
Both applied ONTO upstream's newer files (it rewrote useMedia +150/-63 and
createComponent +160/-55), marked `PATCH (ours, carried across the transplant)`.

Seven traps are encoded in scripts/rebrand.mjs, each found by a gate:
skip itself and lockfiles; special-case the double-branded names in BOTH scoped
and bare form; map path strings, not just paths; drop a level for the flattened
group; check disk rather than a stale index.

Rust build artifacts are NOT committed. An earlier draft of this commit swept
apps/desktop/src-tauri/target/debug in via `git add -A` — 3,859 files including
a 272MB .a, over GitHub's 100MB cap, so the push could never have landed. They
are gitignored now.

Co-Authored-By: Hanzo Dev <[email protected]>
2026-07-30 18:25:06 -07:00

97 lines
3.4 KiB
TypeScript

import { expect, test } from '@playwright/test'
import { setupPage } from './test-utils'
/**
* Regression test for the reanimated avoidReRenders emitter latch bug.
*
* Once a hover fires the useStyleEmitter fast path, the worklet used to latch onto
* its last-emitted snapshot and ignore `animatedStyles` from later re-renders — so a
* base style driven by external state (a sidebar row's `backgroundColor` flipping with
* a selection store) got stuck on the pre-hover value until the next hover. This runs
* against the default reanimated driver, which is where the bug lived.
*/
const bg = (page: import('@playwright/test').Page) =>
page.getByTestId('latch-square').evaluate((el) => getComputedStyle(el).backgroundColor)
test.describe('reanimated emitter latch', () => {
test.beforeEach(async ({ page }) => {
await setupPage(page, {
name: 'ReanimatedEmitterLatchCase',
type: 'useCase',
searchParams: { animationDriver: 'reanimated' },
})
await page.waitForTimeout(300)
})
test('base style change via re-render applies after the element was hovered', async ({
page,
}) => {
const square = page.getByTestId('latch-square')
expect(await bg(page), 'starts inactive (red)').toBe('rgb(255, 0, 0)')
// hover the square — this fires useStyleEmitter and sets the worklet's latch
await square.hover()
await page.waitForTimeout(100)
expect(await bg(page), 'hover shows green').toBe('rgb(0, 255, 0)')
// move the mouse away so we are no longer hovering, then flip `active` through a
// plain React re-render (NOT a hover). the background must follow to the active color.
await page.mouse.move(0, 0)
await page.waitForTimeout(100)
expect(await bg(page), 'unhover returns to inactive red').toBe('rgb(255, 0, 0)')
await page.getByTestId('toggle-active').click()
await page.waitForTimeout(200)
expect(
await bg(page),
'after hovering once, the base bg must still update on re-render (latch bug)'
).toBe('rgb(0, 0, 255)')
// and flipping back must work too
await page.getByTestId('toggle-active').click()
await page.waitForTimeout(200)
expect(await bg(page), 'flips back to inactive red').toBe('rgb(255, 0, 0)')
})
test('named colors interpolate instead of painting the target directly', async ({
page,
}) => {
const samples = await page.evaluate(() => {
return new Promise<string[]>((resolve) => {
const square = document.querySelector('[data-testid="named-color-square"]')!
const button = document.querySelector('[data-testid="toggle-named-color"]')!
const colors: string[] = []
const start = performance.now()
function sample() {
colors.push(getComputedStyle(square).backgroundColor)
if (performance.now() - start < 350) {
requestAnimationFrame(sample)
} else {
resolve(colors)
}
}
;(button as HTMLElement).click()
requestAnimationFrame(sample)
})
})
expect(
samples.some((color) => color !== 'rgb(255, 0, 0)' && color !== 'rgb(0, 0, 255)'),
`expected an intermediate named-color frame, got ${JSON.stringify(samples)}`
).toBe(true)
await expect
.poll(() =>
page
.getByTestId('named-color-square')
.evaluate((element) => getComputedStyle(element).backgroundColor)
)
.toBe('rgb(0, 0, 255)')
})
})