scratchfoundation / scratchfoundation/scratch-blocks
open sounds config will show an error in console
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 1.6k
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 12
Description
Expected Behavior
no error
Actual Behavior
in console show an error, Uncaught (in promise) DOMException: play() failed because the user didn't interact with the document first.
Steps to Reproduce
- change blocks config in scratch-gui, {sounds:true}
- open scratch-gui/index.html
Operating System and Browser
Mac OS 10.13.6 chrome 70.0.3538.102
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 issue from scratch-gui/index.html after changing the blocks configuration to {sounds:true}. Trace the sound-opening path that produces the browser's play() promise error, then verify in Chrome that opening the page no longer logs the reported DOMException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100