On a phone, a signup's page has two links called "Settings" that go to different places
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 76/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- next.js, playwright, react, typescript
- Ambito
- accessibility, frontend
Direzione di ricerca
Inizia da src/app/app/(chrome)/layout.tsx e segui come il link dell’intestazione sceglie l’etichetta per gli schermi stretti e la relativa voce di traduzione. Poi leggi tests/e2e/help/connect-an-ai-assistant.spec.ts e il testo della pagina di aiuto; aggiorna l’etichetta per il telefono e il relativo controllo, mantenendo l’indirizzo email a sm e oltre. Il lavoro è terminato quando l’intestazione a 390px mostra Account, apre /app/settings e la scheda di registrazione rimane Settings.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Needs your OK: this renames the account link in the header on a phone, from "Settings" to "Account". Swap pipeline:proposed for pipeline:ready to have it built.
What happens
On a phone, a signup's page shows "Settings" twice, one above the other:
- The account's, in the header.
src/app/app/(chrome)/layout.tsxshows the organizer's email there fromsmup. Belowsmthe address doesn't fit, so the link says "Settings". It opens/app/settings, where Connected apps lives. - The signup's, in the tab bar.
TabsNav(src/components/signup/TabsNav.tsx) has Build, Responses and Settings. That Settings opens the signup's own settings, such as whether people must give an email.
They lead to different places with the same name. An organizer after the signup's settings can tap the header one and land on Connected apps. On a computer the header shows the email, so the clash only happens below sm (640px).
The header's "Settings" was a deliberate choice when the settings page came in (#225): the comment in the layout says the address won't fit on narrow screens. The signup's Settings tab was already there.
To see it: create a signup and open it at 390px wide. The header reads "Help Settings Sign out". The tabs under the title read "Build Responses Settings".
Fix, in outline
- Call the header link "Account" on a phone. Change its narrow-screen text in
(chrome)/layout.tsxfrom "Settings" to "Account". - Leave the rest of the link alone. It still shows the email from
smup, and itstitlestays "Settings". - Leave the page and the tab alone.
/app/settingskeeps its "Settings" heading and crumb. The signup's Settings tab keeps its name.
Watch for
- Help page.
connect-an-ai-assistantsays "On a phone, it says Settings" and usesUI.settingsfor both the link and the page heading. Add a separateUIentry for the link, and update the text. - e2e tests.
tests/e2e/help/connect-an-ai-assistant.spec.ts, "the header link says Settings", clicks the link by that name at 390px.tests/e2e/organizer.spec.tsfinds it withgetByTitle('Settings'), which still works if thetitlestays.tests/e2e/oauth-consent.spec.tsfinds it byhref, with a comment that names "Settings". Update the comment.
docs/connect-ai-assistant.mdsays to click your email address to open Settings. That's the computer's header, so it stays true.- CHANGELOG: add a line under Unreleased › Changed.
Choices this makes
- "Account", not an icon. The header's other items are words (Help, Sign out), and "Account" fits where "Settings" did.
- Rename the header link, not the tab. "Signup settings" in the tab bar would make it scroll on a phone. The header link already changes its words by screen size.
- The page keeps the name "Settings". Under its heading it says "Signed in as …", so it reads as the account's. Renaming it would change the crumb, the page title, the help page and the docs on a computer too, for a clash that only exists on a phone.
Done when
- At 390px wide, the header link reads "Account" and opens
/app/settings. Fromsmup it still shows the email. - An e2e check at 390px on a signup's page finds the tab named "Settings" and no link named "Settings". (The tabs have
role="tab", so the header link is the only link that could match.) - The help page and its phone e2e say "Account".
pnpm lint && pnpm typecheck && pnpm knip && pnpm testpass.
Found by the UX walkthrough (scenario O4) on 2026-10-24, and checked against the code on main at 4ed27a9.
Generated by Claude Code
- Lingua principale
- TypeScript
- Stelle
- 19
- Fork
- 4
- Merge medio
- 22h 46m
- PR unite (30g)
- 170
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di richshaw/OpenSignup
-
bug pipeline:proposed pipeline:ux
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
richshaw/OpenSignup#711 ·
I maintainer di solito rispondono entro 1 giorno
-
Participant name and notes limits are typed twice, in the schemas and on the participant pagesForse già presa @bfs2021 l’ha presa 2 giorni fa. Apertaenhancement good first issue pipeline:ready
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
richshaw/OpenSignup#705 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement pipeline:proposed pipeline:ux
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
richshaw/OpenSignup#654 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement pipeline:proposed pipeline:ux
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
richshaw/OpenSignup#652 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement pipeline:proposed pipeline:ux
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
richshaw/OpenSignup#588 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di richshaw/OpenSignup
Issue simili
-
bug ready-for-agent
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
PhyberApex/kuroshiro#1687 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
microsoft/monaco-editor#5563 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 86/100
awslabs/visual-asset-management-system#937 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100