Snap Just Broke Due to Undrop Comment

Bug reports Snap! Bugs
1

I can replicate most of the bug:
Screen Recording 2025-03-24 120550.mp4 [video-to-gif output image]
However, when it happened to me while coding, I fiddled a lot more. Eventually I stuck a block in the c-shape (for the block with a comment on it was a c-shaped block), and bam, Snap! froze completely. I had a lot of unsaved work, so I really want to be able to save it. If I recall correctly, there is a way to do it from the developer tools in the browser. If so, I want to do it ASAP in case things get further broken!

PS: Variations on the steps shown above produce differing but similar results.

2

Nevermind about the how to save part, the page is officially kaput, with all my work lost :wink: . Oh well.

3

You may try to see when the latest recovery save was (in the open dialog, press recover).

4

For future problems if it happens again If you want to save it just do “ctrl s” then it will save.

10

It was my impression that the recovery saves weren't auto-saves, but rather were records of previous saves. As for the "restore unsaved project" option in the file menu (sometimes only accessible by shift-click), that might have worked if I had remembered about it in time. I don't know because I only checked that after making the demo for the first post.

Just some clarification, this means that the page was blank and developer tools said it had NO elements.

Thanks for all the suggestions everyone! It turns out that I had less unsaved work than I thought, and was able to recreate it more easily than I thought, so it's fixed now. Whew!

11

From what I remember, that only happens when you open a new project without saving.

14

I can confirm a kind of problem with Chrome@Win10.
Steps to reproduce

  1. Place overlapped blocks
    untitled script pic (1)
  2. Add a comment to the move
    untitled script pic (2)
    untitled script pic (2)430×108 11.3 KB
  3. undrop & redrop
    untitled script pic (3)
    untitled script pic (3)490×118 14 KB
  4. Comment is now unable to stick to the move block
    untitled script pic (4)
    untitled script pic (4)338×104 8.63 KB

    Block or comment morph becomes inconsistent, and further manipulation
  5. Drop the comment to the palette
  6. Drag the move

Leads to (sometimes browser hangs)

blocks.js?version=2025-03-21:16376 Uncaught TypeError: Cannot read properties of null (reading 'position')
    at CommentMorph.startFollowing (blocks.js?version=2025-03-21:16376:61)
    at blocks.js?version=2025-03-21:5967:17
    at Array.forEach (<anonymous>)
    at BlockMorph.prepareToBeGrabbed (blocks.js?version=2025-03-21:5966:24)
    at CommandBlockMorph.prepareToBeGrabbed (blocks.js?version=2025-03-21:6674:47)
    at HandMorph.grab (morphic.js?version=2025-03-20:11324:20)
    at HandMorph.processMouseMove (morphic.js?version=2025-03-20:11607:22)
    at HTMLCanvasElement.<anonymous> (morphic.js?version=2025-03-20:12397:28)
18

When this originally happened, the undrop must've glitched seriously because the block the comment attached itself to was actually about an inch away (on my laptop's screen).

21

yes, it's reproducible and I've already fixed it in my local dev version. But I'm attending a conference this week, and will also be traveling most of next week (and even the week after that), so it might take a while for this fix to make it into production.

22

It's not a huge bug so it's fine

23

Thanks! Enjoy your holiday!

24

How does this even happen?

Also, what happened to half the comments on this post?

25

The off-topic ones were deleted after being flagged.

26

The forum must suddenly have a very strict off-topic policy then

27

(post deleted by author)

28

If you want to discuss moderation policy, start a new thread, please.