scratchfoundation / scratchfoundation/scratch-blocks
Design - Reconcile behaviour when dragging out of the workspace
Open
Nobody has claimed this yet.
design
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 1.6k
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 12
Description
Blockly currently:
- Deletes the block if it's dragged out of the side with the toolbox, no matter how far past the toolbox the drag ends.
- Otherwise drops the block at the point in the workspace nearest the pointer's final position, no matter where the pointer exited the workspace.
Scratch currently:
- Deletes the block if it's dragged into the "flyout" section of the toolbox.
- Adds the blocks to the other sprite and returns them to their original position, if the drag ends on top of a sprite.
- Otherwise returns them to their original position, including if they were dropped on the category section of the toolbox.
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 comparing the documented Blockly and Scratch behaviors for dragging blocks outside the workspace. Define the desired behavior for toolbox, sprite, and other out-of-workspace drops; the issue names no files, tests, or implementation entry point, so those must be identified before work can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100