scratchfoundation / scratchfoundation/scratch-blocks
Detached string inputs float loose in the workspace ("potato blocks")
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 1.6k
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 12
Description
Disconnected string-input shapes appear floating in the workspace ("potato blocks"). They can be typed into but not dragged, and they pop out of the blocks they belong to, particularly custom blocks. The affected blocks often still work at runtime.
Example and diagnosis
A real example: the "load dialogue from compressed string ()" custom block in the NPC sprite of https://scratch.mit.edu/projects/1116676139/ shows a potato block in the top-left of the canvas (reported by @finnagin5).
@nimeratus diagnosed it: there is a text input on the if-else block with the ID uU, which throws an error when Scratch tries to render it. Removing that text input makes the potato block disappear.
May be the same code path as the custom-block-input-deletion bug (scratchfoundation/scratch-blocks#3652).
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
Reproduce the custom-block example from project 1116676139 and inspect the rendering path for the text input with ID uU. Compare the behavior with scratchfoundation/scratch-blocks#3652 and the linked forum report. Done means disconnected string inputs no longer float loose while remaining editable and attached to their blocks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100