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

53 lines
1.6 KiB
TypeScript

import { expect, test } from '@playwright/test'
import { setupPage } from './test-utils'
// Use mobile viewport with touch support (chromium-based to avoid webkit deps in CI)
test.use({
viewport: { width: 390, height: 844 },
hasTouch: true,
isMobile: true,
})
test.beforeEach(async ({ page }) => {
await setupPage(page, { name: 'GroupHoverMobile', type: 'useCase' })
})
test(`group hover styles should not stick after touch on icon`, async ({ page }) => {
const container = page.locator('#group-hover-container')
const text = page.locator('#group-hover-text')
await expect(container).toBeVisible()
await expect(text).toBeVisible()
const iconSvg = container.locator('svg').first()
await expect(iconSvg).toBeVisible()
// Get initial colors
const initialTextColor = await text.evaluate((el) => {
return window.getComputedStyle(el).color
})
const initialIconColor = await iconSvg.evaluate((el) => {
return window.getComputedStyle(el).color
})
// Tap on the container using touchscreen
const box = await container.boundingBox()
if (box) {
await page.touchscreen.tap(box.x + box.width / 2, box.y + box.height / 2)
}
await page.waitForTimeout(300)
// After touch release, both should return to initial color
const afterTouchTextColor = await text.evaluate((el) => {
return window.getComputedStyle(el).color
})
const afterTouchIconColor = await iconSvg.evaluate((el) => {
return window.getComputedStyle(el).color
})
expect(afterTouchTextColor).toBe(initialTextColor)
expect(afterTouchIconColor).toBe(initialIconColor)
})