microsoft / microsoft/pxt-arcade

Keyboard focus jumps to B button after pressing Enter on Menu or Refresh buttons in Simulator

Open
#7,263 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ai-triage keyboardnav p2 simulator
Dominant language
TypeScript
Stars
546
Forks
263
Avg merge
7h 35m
Merged PRs (30d)
46

Description

Describe the bug
When navigating with keyboard Tab inside the Simulator, focusing on the Menu button or Refresh button and pressing Enter causes focus to incorrectly move to the B button instead of activating the selected button.

Steps to reproduce the behavior:
1.Navigate to Microsoft MakeCode Arcade.
2.Open any project and select Keyboard Controls.
3.Pressing Ctrl + B --> 2 and focus on Simulator section.
4.Pressing Tab key and focus on Menu or Refresh button.
5.Pressing Enter and observe the behavior.

Actual behavior
Keyboard focus jumps to B button after pressing Enter on Menu or Refresh buttons in Simulator.

Expected behavior
Pressing Enter should activate the focused button.

Screen recording
Image

Additional context
1.OS: Windows 11 24H2 & MacOS Tahoe 26.1
2.Browser: Microsoft Edge, Chrome, Firefox and Safari
3.Arcade version : 2.1.22
4.Microsoft MakeCode version: 12.2.13

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in the Simulator using the Keyboard Controls flow, then trace the Menu and Refresh button focus and keyboard activation handling. Confirm the fix by checking that pressing Enter activates either focused button without moving focus to the B button, across the reported browsers where available.

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
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.