microsoft / microsoft/pxt-microbit
Global vs Workspace controls split can feel confusing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 804
- Forks
- 721
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 2
Description
Describe the bug
My first action when testing keyboard controls was to open the hints, and start trying to use them; however, when you do that, only a few work. I first wanted to click L to try and download to see an immediate response, but nothing happened; then i tried w to select the workspace, but that also does not work. It sounds like current intention is ctrl+B -> 4 in that scenario to get back, but 'get back to my code' feels like a common action and that's a fairly dense interactoin.
To Reproduce
Steps to reproduce the behavior:
- Go to blocks editor in narrator mode
- control+/ to see keyboard shortcuts
- try to do one of the actions in blocks workspace, because those are the ones that 'feel' most likely to want to be used / take up most of the screen
- See error, the button event is captured in the iframe and does not do anything
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
Reproduce this in the blocks editor using narrator mode: open keyboard shortcuts with Control+/ and try the listed actions inside the blocks workspace. Start by tracing the keyboard shortcut and iframe button-event handling around that workspace. Done means the relevant shortcuts produce their documented actions there, or the controls clearly indicate their scope.
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
- 52/100