e2e: entry paths — typed Room code, unknown code, copied invite #198

New issue

Closed

opened 2026-09-01 13:44:40 +00:00 by root · 4 comments

root commented

2026-09-01 13:44:40 +00:00

(Migrated from gitlab.core-project.space)

Imported from GitHub amaurycoudr/chess-project#198, opened by @amaurycoudr on 2026-09-01 13:44 UTC.
Closed on GitHub on 2026-09-24 13:06 UTC as completed.

Parent

#191

What to build

The three remaining ways a Player arrives at — or fails to arrive at — a Room, grouped because they share one surface and are individually tiny.

Joining by a spoken code. A Player types a Room code a friend read aloud. Ambiguous glyphs are corrected on the way in, so hearing one letter for another does not cost them the game.

A code that leads nowhere. An unknown or expired Room code tells the Player so and returns them home, rather than stranding them on a broken Room. The heading they land on takes focus, so a Player using a screen reader is told where they are.

Copying the invite. A Player copies the invite link in one click and is told it was copied, so they can paste it without transcribing the Room code.

Acceptance criteria

A Player joins an existing Room by typing its Room code on the home page and takes the free Seat
A Room code typed with ambiguous glyphs still reaches the right Room
Submitting the code field with the keyboard works, not only clicking the button
An unknown Room code shows the Player a message and returns them to the home page
The Room code is displayed prominently while a Seat is still free
Copying the invite link tells the Player it was copied, with clipboard permission granted to the browser context
The copied link, opened in another context, reaches the same Room
All five gate commands pass, and the suite passes

> _Imported from GitHub [amaurycoudr/chess-project#198](https://github.com/amaurycoudr/chess-project/issues/198), opened by [@amaurycoudr](https://github.com/amaurycoudr) on 2026-09-01 13:44 UTC._ > _Closed on GitHub on 2026-09-24 13:06 UTC as completed._  --- ## Parent #191 ## What to build The three remaining ways a Player arrives at — or fails to arrive at — a Room, grouped because they share one surface and are individually tiny. **Joining by a spoken code.** A Player types a Room code a friend read aloud. Ambiguous glyphs are corrected on the way in, so hearing one letter for another does not cost them the game. **A code that leads nowhere.** An unknown or expired Room code tells the Player so and returns them home, rather than stranding them on a broken Room. The heading they land on takes focus, so a Player using a screen reader is told where they are. **Copying the invite.** A Player copies the invite link in one click and is told it was copied, so they can paste it without transcribing the Room code. ## Acceptance criteria - [ ] A Player joins an existing Room by typing its Room code on the home page and takes the free Seat - [ ] A Room code typed with ambiguous glyphs still reaches the right Room - [ ] Submitting the code field with the keyboard works, not only clicking the button - [ ] An unknown Room code shows the Player a message and returns them to the home page - [ ] The Room code is displayed prominently while a Seat is still free - [ ] Copying the invite link tells the Player it was copied, with clipboard permission granted to the browser context - [ ] The copied link, opened in another context, reaches the same Room - [ ] All five gate commands pass, and the suite passes

root commented

2026-09-01 13:44:40 +00:00

(Migrated from gitlab.core-project.space)