scratchfoundation / scratchfoundation/scratch-editor
Reordering sprites when a sprite is newer than a clone
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 281
- Forks
- 276
- Avg merge
- 7d 8h
- Merged PRs (30d)
- 6
Description
Expected Behavior
When dropping the sprite thumbnail, it moves to the position of its shadow
Actual Behavior
The dragged sprite moves back to its original position, and the other 3 sprites are mixed
Steps to Reproduce
- Add 3 sprites to a project
- Click on a
make clone of (myself v)block - Add a new sprite
- Try to drag the new sprite to the first position
System Details
Windows 10, Chrome 138
Screenshots
https://github.com/user-attachments/assets/e1c865e1-bb34-4088-bc35-2ad3f9b566ef
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 in scratch-editor using the listed sprite, clone, and drag-and-drop steps in Chrome on Windows. Trace the sprite thumbnail reordering behavior when a newer sprite and a clone are present. Done means the dragged sprite moves to the position of its shadow and the other sprites retain their correct order.
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
- 45/100