You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several issues have popped up after the recent Scratch editor release, which includes the "spork" (Blockly unforking) work in scratch-blocks. This is a meta-issue to track them. We should file individual issues for each at some point, but that's probably after the most urgent items are hotfixed.
Status (2026-04-30): two waves of fixes deployed (2026-04-21 and 2026-04-29). Backpack/broadcast de/serialization fixes (#554 + #555) merged today into the hotfix branch — not yet deployed to production. One community PR still open: #3571 (hat block delete preserves stack), CI clean, awaiting review. Custom block input deletion cursed inputs and the related "potato block" reports are the next fix priority.
P0 -- Data loss / code deletion
✅ Disappearing blocks on project load. Fixed by #3547 + argumentdefaults follow-up.
Cursed inputs from custom block input deletion NOT fixed. Deleting a custom block input still creates a cursed/blank input. Confirmed still reproducible by @nimeratus and @redspacecat (2026-04-22). May share a code path with the "detached input fragments" reports below. Top fix priority.
Variable names mangled (shared "my variable" IDs across projects).
Backpack broadcasts don't define the broadcast variable, so they can never fire (@nimeratus analysis). Independently re-confirmed by pippy2011eight (2026-04-29).
Detached string input fragments in custom blocks ("potato blocks"). Disconnected string input shapes appear floating in the workspace, can be typed into but not dragged. Reported by fortyonegames; ywc2 notes they "pop out of blocks they originally belonged to, particularly from custom blocks." Likely shares a code path with the custom block input deletion cursed input bug.
Repro confirmed by @kaylen-s: dragging blocks into stacks behind the palette can delete unintended parts of the stack. (2026-04-30)
🤔 Sprite duplication causes code loss. All reports pre-date the 2026-04-21 hotfix; QA suggests this is likely fixed by one of the earlier hotfixes (probably the shared-shadow-ID fix in #3560/#3563). Needs re-verification on the current build.
Old projects: blocks disappear on load and block palette tab disappears + can't be reopened. Reported on ChromeOS Chrome 146. May be aftermath of cursed inputs in saved projects from before the 2026-04-21 hotfix.
RTL editor interactions malfunction: reversed text and operators, erratic drag behavior, and custom blocks can disappear off-screen, making the editor unusable in affected languages.
Received a Freshdesk report from a Hebrew language program with ~100 students who are experiencing significantly disrupted classroom use
P2 -- Blocks editing broken
"Create new broadcast/message" dialog closes immediately.
Sprite costumes skipped when running a tight next costume + wait 0.1 loop over 100+ costumes. Likely runtime/timing rather than spork. https://scratch.mit.edu/discuss/topic/881012/
"Property of sprite" block deletes itself when changing the sprite dropdown. Workaround: edit in the sidebar first.
Undo in costume editor replaces entire sprite with previous sprite. Hitting undo "too many times" in the costume editor reverts so far that the current sprite is replaced by the previously-edited sprite. Single report so far on ChromeOS / Chrome 132.
Several issues have popped up after the recent Scratch editor release, which includes the "spork" (Blockly unforking) work in scratch-blocks. This is a meta-issue to track them. We should file individual issues for each at some point, but that's probably after the most urgent items are hotfixed.
Big thanks to @redspacecat, @nimeratus, @mxmou, @Joeclinton1, @npxl32, and others for collecting reports and contributing technical analysis. See the comments on this issue for the running feed. There is also a community-maintained list at https://scratch.mit.edu/discuss/post/9109627/
Status (2026-04-30): two waves of fixes deployed (2026-04-21 and 2026-04-29). Backpack/broadcast de/serialization fixes (#554 + #555) merged today into the hotfix branch — not yet deployed to production. One community PR still open: #3571 (hat block delete preserves stack), CI clean, awaiting review. Custom block input deletion cursed inputs and the related "potato block" reports are the next fix priority.
P0 -- Data loss / code deletion
stripIdsmutated original block'sconnection.shadowStateby reference, creating orphaned top-level shadows that prevent workspace rendering on sprite switch. Diagnosis from @nimeratus, clear repro from @Joeclinton1.P1 -- Silent wrong behavior / runtime failures / interaction failures
P2 -- Blocks editing broken
P3 -- Visual / cosmetic regressions
box-sizing: border-boxmissing in production. Fix identified by @mxmou.P4 -- Performance / viewport
P5 -- Low-confidence / adjacent / unreproduced
next costume+wait 0.1loop over 100+ costumes. Likely runtime/timing rather than spork. https://scratch.mit.edu/discuss/topic/881012/