scratchfoundation / scratchfoundation/scratch-editor
Verify: sprite duplication no longer causes code loss
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 281
- Forks
- 276
- Avg merge
- 7d 8h
- Merged PRs (30d)
- 6
Description
Duplicating a sprite was reported to drop or lose code. All reports pre-date the April 2026 hotfixes, and this is believed resolved by the shadow-ID fix deployed 2026-04-29 (scratchfoundation/scratch-blocks#3570, scratchfoundation/scratch-editor#543) or an earlier hotfix. Filing this so the fix can be confirmed on the live site and closed, rather than assumed.
If you can still reproduce code loss when duplicating a sprite on the current scratch.mit.edu, please comment with steps.
Part of scratchfoundation/scratch-editor#533.
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 on the current scratch.mit.edu site and reproduce the reported sprite-duplication workflow, checking whether the duplicated sprite retains its code. Compare the result with the shadow-ID fixes in scratchfoundation/scratch-blocks#3570 and scratchfoundation/scratch-editor#543; done means confirming the issue is resolved or commenting with reproducible steps if code loss remains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100