Monitor context menus shrink the Editor

Open
#744 6 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

@mxmou is already working on this.

Since Nov 4, 2026.

  • #747 by @mxmou — open

Assessment

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

Research direction

Start by reproducing the issue on the main site: display a variable monitor and open its context menu. Then trace the monitor and context-menu entry points in the editor to find what causes the editor height to change. Done means opening the menu no longer shrinks the editor.

Written by the indexing model from the issue text.

Description

Expected Behavior

The editor should probably stay the same height.

Actual Behavior

The editor shrinks (???)

Steps to Reproduce

  • Go to any project on the main site, or create a fresh one (quicker).
  • Display a variable monitor.
  • Context click (The one that brings up a menu, typically the right mouse button, or holding using a touch input) on the monitor.
  • And then, behold:
Image

Demonstration:

https://github.com/user-attachments/assets/ea593187-570e-402b-bb2e-af6d690bc35b

System Details

This has been tested on both Firefox and Chromium.
It happens to users of Microsoft Windows, ChromeOS, and Ubuntu-based and Arch Linux.

I run KDE neon (which is Ubuntu-based) and use Native Firefox and Flatpak Chromium.

  [Firefox Native] Mozilla/5.0 (X11; Linux x86_64; rv:157.0) Gecko/20100101 Firefox/157.0
[Chromium Flatpak] Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/152.0.0.0 Safari/537.36
 [ChromeOS Chrome] Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit 537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36 

I have known about this bug since October 6th, when I posted about it in BaG. Additional screenshots can be found there.

Dominant language
JavaScript
Stars
310
Forks
299
Avg merge
19h 41m
Merged PRs (30d)
14

Getting set up

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.

More from scratchfoundation/scratch-editor

All issues in scratchfoundation/scratch-editor

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.