Blank cells in Jupyter Notebooks and other files after scrolling, requires full window reload

[KyleYueye]

Is there an existing issue for this?

• [x] I have searched the existing issues

OS/Web Information

• Web Browser: Google Chrome Canary
• Local OS: MacOS Tahoe
• Remote OS: Ubuntu 22.04
• Remote Architecture: amd64
• code-server --version: 4.106.3

Steps to Reproduce

1. Open any Jupyter Notebook (.ipynb file) in VS Code
2. Scroll up/down vertically 3-5 times (sometimes occurs after aggressive scrolling)
3. Observe all notebook cells turn blank with no content visible
4. Switch to any other file type (Python script, text file, CSV, etc.)
5. Confirm all file contents are also blank/unrendered
6. Attempt to fix via: Reload Webview → No effect
7. Only solution: Full window reload, but it'll reappear soon after.

Expected

Normal usage of jupyter notebook

Actual

After opening a Jupyter Notebook (.ipynb) in code-server and scrolling vertically a few times, all notebook cells become completely blank (no code/output visible). This corruption persists across all file types (.py, .txt, .csv, etc.) until a full window reload is performed. Reloading the webview alone has no effect.

Logs

Not found strongly relevant logs

Screenshot/Video

Does this bug reproduce in native VS Code?

I did not test native VS Code

Does this bug reproduce in VS Code web?

I did not test VS Code web

Does this bug reproduce in GitHub Codespaces?

I did not test GitHub Codespaces

Are you accessing code-server over a secure context?

• [x] I am using a secure context.

Notes

No response

[code-asher]

I attempted to reproduce by creating a bunch of cells (seven) with print calls and then scrolling up and down on Firefox and Chromium (I tried my mouse scroll wheel and also dragging the scrollbar up and down violently) but the cells are not disappearing for me.

Does it only happen with a specific notebook? Could you test on Codespaces or VS Code web to see if the issue is isolated to code-server or is an upstream problem?

[KyleYueye]

Okay, it seems to be a Chrome Canary issue since it appears right in OpenVSCode Server I've just installed

[partev]

I have this issue on Chrome 144.0.7559.4

[code-asher]

I will go ahead and mark this as an upstream issue in that case! Looks like it might be this issue: https://github.com/microsoft/vscode/issues/277655