scratchfoundation / scratchfoundation/scratch-blocks
Dragging a stack behind the palette can delete part of it
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 1.6k
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 12
Description
While dragging a block, you can connect it to blocks that sit behind the block palette. When you release, it connects and deletes all blocks below the connection point — silent code loss.
- Repro video (@redspacecat): https://github.com/user-attachments/assets/23ff8511-103d-4ec2-abe3-d9c4fea4e8fc
- Forum: https://scratch.mit.edu/discuss/post/9112451/
Reported by @redspacecat; repro confirmed by @kaylen-s.
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
No files or tests are named. Start by reproducing the drag-and-release behavior using the linked video, then trace the block dragging and connection handling in Scratch Blocks. Done means dragging near or behind the palette cannot connect to hidden blocks or delete the remainder of a stack, with existing behavior still intact.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100