microsoft / microsoft/pxt-microbit
Cannot select a music note using piano keyboard on Android Tablet
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 804
- Forks
- 721
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 2
Description
Describe the bug
Using the latest makecode editor on an Android tablet using Chrome the piano keyboard doesn't show so you can't select a note. It just shows a numeric value for the note. If you use the makecode version 2 editor with the same setup it does work.
To Reproduce
Steps to reproduce the behavior:
- Using an android tablet on Android 12 and a chrome browser go to makecode.microbit.org
- Start a new project
- Under music move play tone Middle C for 1 beat to the work area.
- Try and change the note. The keyboard flashes up and disappears and you get a change value screen with a numeric value showing.
Expected behavior
It should display a piano keyboard. If you switch to version 2 of the editor it works as expected.
Screenshots
Add screenshots to help explain your problem. You can copy paste the screenshot in the github report. The .gif screen recording is very useful as well.
**micro:bit version Nothing to do with the Micro:bit version.
**Android Tablet
- Device: Samsung Galaxy Tab A7 SM-T505
- OS:Android 12
- Browser Chrome
- Version 110.0.5481.153
Additional context
Add any other context about the problem here.

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 at makecode.microbit.org in Chrome on an Android 12 tablet and reproduce the issue by adding Music's “play tone Middle C for 1 beat” block, then compare the same steps in the version 2 editor. Done means changing the note consistently displays and keeps the piano keyboard instead of switching to a numeric value screen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100