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 (#3652).
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 (#3652).