diff --git a/ui/e2e/social.spec.ts b/ui/e2e/social.spec.ts index fe12a2a..1562d9a 100644 --- a/ui/e2e/social.spec.ts +++ b/ui/e2e/social.spec.ts @@ -292,14 +292,14 @@ test('profile edit disables Save and flags an invalid display name', async ({ pa await expect(save).toBeEnabled(); }); -// Account linking is hidden in Profile.svelte while we target provider sign-in (the anonymous -// /app/ guest who upgrades by linking comes later). The flow is kept wired; re-enable these two -// specs together with the `.emailbox` section. +// The email upgrade box is now shown to guests (email bind + the merge dialog). These specs +// still assume a non-guest login and the visible Telegram control, so they stay skipped until +// PR2 re-enables provider linking and adds a guest-login setup. test.skip('link account: a taken email opens the irreversible merge confirmation', async ({ page }) => { await loginLobby(page); await openProfile(page); - // The linking section is shown to everyone (guests upgrade by linking). + // The email box is shown to guests (this spec needs a guest login — re-enabled in PR2). await expect(page.getByRole('heading', { name: 'Link an account' })).toBeVisible(); // An address containing "merge" stands in (in the mock) for one already owned by // another account, so the confirm step reveals a required merge. diff --git a/ui/src/screens/Profile.svelte b/ui/src/screens/Profile.svelte index f12a500..8590b3a 100644 --- a/ui/src/screens/Profile.svelte +++ b/ui/src/screens/Profile.svelte @@ -244,10 +244,11 @@ {/if} - -