google / blockly

The web-based visual programming editor.
https://developers.google.com/blockly/
Apache License 2.0
12.5k stars 3.71k forks source link

Multi-line block comments break when scrollbars should appear on Safari #8160

Open cpcallen opened 5 months ago

cpcallen commented 5 months ago

Check for duplicates

Description

In Safari 17.4.1 on macOS 13.6.6, when a multi-line block comment exceeds the height of the textarea, the textarea completely disappears.

Reproduction steps

  1. Load the playground in Safari.
  2. Add a block (e.g. controls_if) to the workspace.
  3. Right click on the block and choose "add comment"
  4. Click on question-mark icon to open block comment bubble.
  5. Type "blah" and press enter. Repeat until text is too tall for textarea.

Stack trace

No response

Screenshots

Note screenshots display an unrelated text positioning bug that was caused by #8158. This bug was not caused by #8158 and can be observed at commit 36b7569.

Screenshot 2024-05-20 at 17 51 47 Screenshot 2024-05-20 at 17 51 54 Screenshot 2024-05-20 at 17 51 15

Browsers

No response

cpcallen commented 5 months ago

@maribethb reports she was able to reproduce.

I can reproduce in v10.4.3, so it is not a regression in v11.

NeilFraser commented 5 months ago

This is reproducible in Blockly Games which uses a version of Blockly that's several years old. There is absolutely no way that this bug could have lurked undetected for so long. Thus the logical conclusion is that this is a recent regression in Safari.

Also, I can now reproduce it on my computer. The key is that System Settings > Appearance > Scrollbars should be set to "When scrolling" to trigger the bug. If Scrollbars are set to "Always" then the bug doesn't manifest.

This is 100% a bug in Safari itself (or OS X).

NeilFraser commented 5 months ago

Created a minimal testcase and filed a bug with Webkit: https://bugs.webkit.org/show_bug.cgi?id=274408

BeksOmega commented 5 months ago

Closing since this isn't our bug.

cpcallen commented 2 months ago

Reopening this until it gets fixed in Safari so we don't get further duplicate reports.