microsoft / microsoft/pxt-microbit
Keyboard nav: duplicating blocks via the context menu should put you in move mode
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 804
- Forks
- 721
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 2
Description
When a user duplicates a block, I think the likelihood that they would want to move that block is pretty high. However, with keyboard navigation, the block that you just created from duplication is not in move mode. This feels a bit jarring because when you select a block from the toolbox, it is in move mode by default. My suggestion would be to have duplicated blocks in move mode by default, just as we have blocks that a user takes from the toolbox.
To Reproduce
Steps to reproduce the behavior:
- Go to beta
- Open a new project
- Add some blocks to your project
- Open the context menu on a block with keyboard navigation (control+enter)
- Select duplicate with keyboard navigation
- See that the duplicated block is not in move mode
Desktop (please complete the following information):
- OS: Windows and Mac
- Browser Edge and Chrome
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
No file or test path is named; start by tracing the keyboard context-menu duplicate action and compare it with the toolbox block-insertion path. Reproduce the listed steps in beta, then verify that a duplicated block enters move mode and that existing keyboard navigation behavior remains intact.
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
- 68/100