mirror of
https://github.com/hanzoai/gui.git
synced 2026-10-25 02:31:41 +00:00
zeekayandHanzo Dev
69c6e860d7
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]>
80 lines
2.5 KiB
TypeScript
80 lines
2.5 KiB
TypeScript
import { expect, test, type Page } from '@playwright/test'
|
|
import { setupPage } from './test-utils'
|
|
|
|
/**
|
|
* TooltipGroup Tests
|
|
*
|
|
* TooltipGroup enables grouped delay behavior:
|
|
* - First tooltip in group: waits for full delay
|
|
* - Subsequent tooltips: show immediately while within the group's timeout window
|
|
*
|
|
* This is implemented via FloatingDelayGroup from @hanzogui/floating.
|
|
*/
|
|
|
|
async function tooltipVisible(page: Page, testId: string): Promise<boolean> {
|
|
return page.evaluate((id) => !!document.querySelector(`[data-testid="${id}"]`), testId)
|
|
}
|
|
|
|
test.describe('TooltipGroup', () => {
|
|
test.beforeEach(async ({ page }) => {
|
|
await setupPage(page, { name: 'TooltipGroupCase', type: 'useCase' })
|
|
})
|
|
|
|
test('subsequent grouped tooltips skip delay', async ({ page }) => {
|
|
// Config: 1000ms open delay, 500ms timeout
|
|
const DELAY = 1000
|
|
|
|
// Show first tooltip (with delay)
|
|
await page.getByTestId('tooltip-trigger-1').hover()
|
|
await page.waitForTimeout(DELAY + 200)
|
|
expect(await tooltipVisible(page, 'tooltip-content-1')).toBe(true)
|
|
|
|
// Move to second tooltip - should appear quickly (no full delay)
|
|
await page.getByTestId('tooltip-trigger-2').hover()
|
|
await page.waitForTimeout(300)
|
|
|
|
expect(
|
|
await tooltipVisible(page, 'tooltip-content-2'),
|
|
'Second grouped tooltip should appear without waiting for full delay'
|
|
).toBe(true)
|
|
})
|
|
|
|
test('first grouped tooltip respects delay', async ({ page }) => {
|
|
const DELAY = 1000
|
|
|
|
await page.getByTestId('tooltip-trigger-1').hover()
|
|
|
|
// Should NOT appear before delay
|
|
await page.waitForTimeout(200)
|
|
expect(
|
|
await tooltipVisible(page, 'tooltip-content-1'),
|
|
'Should not appear before delay'
|
|
).toBe(false)
|
|
|
|
// Should appear after delay
|
|
await page.waitForTimeout(DELAY)
|
|
expect(
|
|
await tooltipVisible(page, 'tooltip-content-1'),
|
|
'Should appear after delay'
|
|
).toBe(true)
|
|
})
|
|
|
|
test('standalone tooltips always have delay', async ({ page }) => {
|
|
const DELAY = 1000
|
|
|
|
// Show standalone A
|
|
await page.getByTestId('tooltip-trigger-standalone-a').hover()
|
|
await page.waitForTimeout(DELAY + 200)
|
|
expect(await tooltipVisible(page, 'tooltip-content-standalone-a')).toBe(true)
|
|
|
|
// Move to standalone B - should NOT appear quickly (has its own delay)
|
|
await page.getByTestId('tooltip-trigger-standalone-b').hover()
|
|
await page.waitForTimeout(300)
|
|
|
|
expect(
|
|
await tooltipVisible(page, 'tooltip-content-standalone-b'),
|
|
'Standalone tooltips should always wait for their delay'
|
|
).toBe(false)
|
|
})
|
|
})
|