scratchfoundation / scratchfoundation/scratch-editor

Uploading a project doesn't update monitor positions

Open
#322 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
281
Forks
276
Avg merge
7d 8h
Merged PRs (30d)
6

Description

https://scratch.mit.edu/discuss/topic/838720/

Expected Behavior

Monitors appear as they were saved in the file

Actual Behavior

Monitors appear where they were before opening the file

Steps to Reproduce

Steps to reproduce the behavior:

  1. Go to 'https://scratch.mit.edu/projects/editor/'
  2. Show a variable and a list
  3. Move the variable and the list to the bottom left corner
  4. Save the project to your computer
  5. Move the variable and the list to somewhere else
  6. Load the saved project
    Note: The variable and the list didn't return to the saved position
System Details

I've tested it on Windows 10, Chrome 140

Screenshots

https://github.com/user-attachments/assets/4b59e344-23ad-415f-96d7-3fc618100be7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue at https://scratch.mit.edu/projects/editor/ using the listed steps, then inspect the project upload and monitor-position restoration path. Compare the saved project data with the monitor positions after loading; done means variables and lists return to their saved positions.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.