microsoft / microsoft/pxt-microbit
Default keyboard: Focus is lost after pressing Enter on the "Close" button in the User menu
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 804
- Forks
- 721
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 2
Description
Describe the bug
When navigating using the default keyboard, focus is lost after pressing the Enter key on the "Close" button within the My Profile dialog accessed from the User menu.
Steps to reproduce the behavior:
- Navigate to https://makecode.microbit.org/beta.
- Sign in with a valid Microsoft account.
- Press Tab repeatedly until focus is on the User menu button.
- Press Enter twice to open the My Profile dialog.
- Press Tab repeatedly until focus moves to the "Close" button.
- Press Enter and observe the focus behavior.
Actual behavior
After pressing Enter on the "Close" button, the dialog closes but focus is lost. No visible focus indicator is present on the page.
Expected behavior
After pressing Enter on the "Close" button and closing the dialog, focus should return to the User menu button to maintain logical focus order and support accessible keyboard navigation.
Screen Recording
https://github.com/user-attachments/assets/4a24fd95-e550-4fa2-86ab-503dd21a55e0
Additional context
1.OS: Windows 11 25H2 & Mac Mini M2 macOS Tahoe 26.5
2.Browser: Chrome, Edge, Firefox, and Safari
3.makecode.microbit.org version: 8.1.17
4.Microsoft MakeCode version: 12.3.12
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue at makecode.microbit.org/beta using the User menu and My Profile dialog, then trace the keyboard handling for the dialog's Close button and User menu button. Done means pressing Enter on Close closes the dialog and visibly returns focus to the User menu button, with keyboard navigation still working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100