The checkboxes for sprite-specific monitors don't connect to the right monitors
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by reproducing the issue at https://scratch.mit.edu/projects/editor/ using the listed steps, checking monitor toggles while switching between the Stage and sprites. Trace the sprite-specific monitor checkbox behavior from that editor entry point; done means each checkbox toggles only the currently selected sprite's monitor once, without duplicate monitors.
Written by the indexing model from the issue text.
Description
https://scratch.mit.edu/discuss/topic/905757/
Expected Behavior
The checkboxes always toggle those monitors that show the current sprite's properties.
Actual Behavior
The checkboxes are connected to a set of monitors that depends on the sprite that was selected when the checkboxes loaded. For example if a checkbox was loaded by going from the Stage to Sprite1, and then you switch to Sprite2 and show Sprite2's monitor, then Sprite2's monitor is added to Sprite1's set. Then if you go back to the Stage, you can hide the monitor only if you first go to Sprite1
Steps to Reproduce
Steps to reproduce the behavior:
- Go to 'https://scratch.mit.edu/projects/editor/'
- Show the 'x position'
- Create and select a new sprite (I'll call it Sprite2)
- See that the 'x position' checkbox is still toggling Sprite1's monitor
- Show the 'y position'
- Go to the Stage and go back to Sprite2
- Click again on the 'y position' checkbox
- See that it now shows it two times instead of hiding the first one
- Go to the Stage and then go to Sprite1
- Click again on the 'y position' checkbox
- See that it now hides Sprite2's first monitor, even though Sprite1 is selected
Screenshots
https://github.com/user-attachments/assets/cb716e34-e6c7-41a9-9b85-dda47c679187
System Details
I've tried it in the online editor on Windows 10, Chrome 154
According to the forum, it also happens in Scratch Desktop (Offline Editor) v3.32.1, but it doesn't in v3.29.1
- Dominant language
- JavaScript
- Stars
- 310
- Forks
- 299
- Avg merge
- 19h 41m
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from scratchfoundation/scratch-editor
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
scratchfoundation/scratch-editor#754 ·
Maintainers usually reply within 1 day
-
spork
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
scratchfoundation/scratch-editor#646 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
scratchfoundation/scratch-editor#406 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
scratchfoundation/scratch-editor#750 · 1 comment ·
Maintainers usually reply within 1 day
-
Monitor context menus shrink the EditorPossibly taken @mxmou claimed this 3 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 50/100
scratchfoundation/scratch-editor#744 · 6 comments · 1 reaction ·
Maintainers usually reply within 1 day
All issues in scratchfoundation/scratch-editor
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 96/100
google/site-kit-wp#14102 ·
Maintainers usually reply within 2 days
-
area:growth priority:P1 type:docs
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
tecnologiasantos/bogoboom#66 ·
Maintainers usually reply within 1 day
-
desktop docs good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
npm/write-file-atomic#245 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ktwu01/benchmark-radar#1181 ·
Maintainers usually reply within 1 day