Files
gui/apps/kitchen-sink/tests/ExitTimingCheck.animated.test.ts
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

35 lines
1.3 KiB
TypeScript

import { test, expect } from '@playwright/test'
import { setupPage } from './test-utils'
test('exit animation holds element during tab switch', async ({ page }) => {
// native driver has hover/animation issues on web
const driver = (test.info().project?.metadata as any)?.animationDriver
test.skip(driver === 'native', 'native driver has element detection issues on web')
await setupPage(page, { name: 'TabHoverAnimationCase', type: 'useCase' })
await page.waitForTimeout(500)
await page.locator('[data-testid="tab-tab-a"]').hover()
await page.waitForTimeout(400)
const content = page.locator('[data-testid="slide-content"]')
expect(await content.count()).toBe(1)
await page.locator('[data-testid="tab-tab-d"]').hover()
await page.waitForTimeout(60)
const countAt60 = await content.count()
const elemsAt60 = await page.evaluate(() =>
Array.from(document.querySelectorAll('[data-testid="slide-content"]')).map((el) => ({
tab: (el as HTMLElement).dataset.tab,
opacity: getComputedStyle(el).opacity,
}))
)
console.log(`At 60ms - count: ${countAt60}, elements: ${JSON.stringify(elemsAt60)}`)
// If exit animation works: 2 elements (A exiting + D entering)
// If exit is immediate: 1 element (only D)
expect(countAt60).toBe(2)
})