Files
gui/apps/kitchen-sink/tests/GroupDisabledStyleLatch.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

95 lines
3.4 KiB
TypeScript

import { expect, test } from '@playwright/test'
import { setupPage } from './test-utils'
/**
* Regression test for the group + disabledStyle emitter latch bug (Wez, June 2026).
*
* A `group` frame with pressStyle goes through the avoidReRenders style emitter:
* the press that toggles `disabled` latches the worklet onto its last-emitted
* snapshot. The disabled re-render merges disabledStyle into the base style, but
* before the latch-drop fix the worklet kept painting the stale latched green —
* the circle never went grey even though a child label re-rendered fine. Runs
* against the reanimated driver where the latch lives.
*/
const color = (
page: import('@playwright/test').Page,
id: string,
prop: 'backgroundColor' | 'borderTopColor'
) => page.getByTestId(id).evaluate((el, p) => getComputedStyle(el)[p], prop)
const GREEN = 'rgb(27, 122, 61)'
const GREY = 'rgb(217, 215, 210)'
test.describe('group + disabledStyle emitter latch', () => {
test.beforeEach(async ({ page }) => {
await setupPage(page, {
name: 'GroupDisabledStyleLatchCase',
type: 'useCase',
searchParams: { animationDriver: 'reanimated' },
})
await page.waitForTimeout(300)
})
test('disabledStyle applies after the press that latched the emitter', async ({
page,
}) => {
const pressBtn = 'group-disabled-press-btn'
const plainBtn = 'group-disabled-btn'
expect(await color(page, pressBtn, 'backgroundColor'), 'starts green').toBe(GREEN)
expect(await color(page, plainBtn, 'backgroundColor'), 'starts green').toBe(GREEN)
// the press itself goes through the emitter (pressStyle), then onPress flips
// disabled via a React re-render whose base style must win over the latch
await page.getByTestId(pressBtn).click()
await expect(page.getByTestId('group-disabled-state')).toHaveText('disabled')
await expect
.poll(() => color(page, pressBtn, 'backgroundColor'), {
message: 'pressed frame settles grey when disabled',
timeout: 3000,
})
.toBe(GREY)
await expect
.poll(() => color(page, pressBtn, 'borderTopColor'), {
message: 'pressed frame border settles grey when disabled',
timeout: 3000,
})
.toBe(GREY)
// the minimized frame (no press/hover styles) follows through the plain re-render
await expect
.poll(() => color(page, plainBtn, 'backgroundColor'), {
message: 'minimized frame settles grey when disabled',
timeout: 3000,
})
.toBe(GREY)
// re-enable via the external toggle (the disabled circles ignore presses)
await page.getByTestId('group-disabled-toggle').click()
await expect(page.getByTestId('group-disabled-state')).toHaveText('enabled')
await expect
.poll(() => color(page, pressBtn, 'backgroundColor'), {
message: 'pressed frame settles back to green',
timeout: 3000,
})
.toBe(GREEN)
await expect
.poll(() => color(page, plainBtn, 'backgroundColor'), {
message: 'minimized frame settles back to green',
timeout: 3000,
})
.toBe(GREEN)
// a second press-disable cycle still works (latch was re-set by the press)
await page.getByTestId(pressBtn).click()
await expect(page.getByTestId('group-disabled-state')).toHaveText('disabled')
await expect
.poll(() => color(page, pressBtn, 'backgroundColor'), {
message: 'second disable settles grey',
timeout: 3000,
})
.toBe(GREY)
})
})