scratchfoundation / scratchfoundation/scratch-desktop
alert or confirm makes Scratch Desktop unable to receive input
Open
Nobody has claimed this yet.
bug
High Severity
Low Impact
priority 3
- Dominant language
- JavaScript
- Stars
- 426
- Forks
- 268
- Avg merge
- 16h 6m
- Merged PRs (30d)
- 25
Description
Expected Behavior
You can type on input
Actual Behavior
If alert() or confirm() is executed, you cannot type on inputs anymore, until you blur and re-focus the window. This only happens in Scratch Desktop 3.9.0.
Steps to Reproduce
There are three ways to get into this state:
- Do something (so that opening a project gives warning), open a project, click ok
- Click load from computer, open a file that is not sb3 (like a txt), and get invalid project alert
- Disable mic via privacy setting and try to record voice
- After doing one of them, try editing the sprite info (sprite name) or variable name.
- You can't type, but can paste.
- Choose other window (like firefox or notepad) and focus Scratch Desktop again and you can type again.
Operating System and Browser
Windows 10, Scratch Desktop 3.9.0 (exe)
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 alert() or confirm() flow in Scratch Desktop 3.9.0 on Windows 10, especially the invalid-project alert or voice-recording warning. Check that sprite-name and variable-name inputs accept typing immediately afterward without switching windows or blurring and refocusing Scratch Desktop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100