Pressing the "down arrow" key triggers unexpected behaviour in Notebook

Describe the Bug

Pressing the “down key” in the python notebook causes an error (or warning - i am not sure) to popup that reads “Cannot read properties of undefined (reading ‘fontSize’)”.

Steps to Reproduce

Open a python notebook.

In a cell, type something, multi-line. When you use the arrow keys to go “up” and “down” with the (text) cursor, if you go down and read the last row of the cell, the effect is triggered.

Same happens if you are in so-called “command mode”.

Expected Behavior

If you reach the bottom of the cell and you keep pressing down, the text cursor should go to the next cell bellow that (if it exists; if not, nothing you are at the bottom).

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.0
VSCode Version: 1.99.3
Commit: 3c325775412a19b2f2147eed6b33f36371f025b0
Date: 2025-07-01T11:16:12.951Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Additional Information

While this does not break the base functionality of Cursor, it significantly degrades the user experience while using the notebook.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Same issue here — pressing ↓ in .ipynb cells throws ‘Cannot read properties of undefined (reading fontSize)’ and I can’t switch cells unless I press ESC. I’m using Cursor version 1.2.1 on macOS.

Can confirm, super annoying issue. Cursor 1.2 on Windows (WSL)

Exactly the same thing for me. Same error message pops up also when I press the arrow key upwards at the first row of the cell, but in that case the cursor moves to the above cell. The same error message also pops up, when I run a cell with shift+enter or enter into a cell with enter.

My cursor specifications:

Version: 1.2.2
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:08:52.104Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.3.0

Precisely the same issue, very disruptive.

Version: 1.2.2
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:08:52.104Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.4.0

Same issue here. Need to be fixed right away.

image

제발 해결해주세요.

Same issue
OS: Ubuntu 24.04
Cursor version: 1.2.2
VSCode version: 1.102.0

Same issue with:
Version: 1.2.4

VSCode Version: 1.99.3

Commit: a8e95743c5268be73767c46944a71f4465d05c90

Date: 2025-07-10T16:53:59.659Z (5 days ago)

Electron: 34.5.1

Chromium: 132.0.6834.210

Node.js: 20.19.0

V8: 13.2.152.41-electron.0

OS: Darwin arm64 24.5.0

facing the same issue in Jupyter Notebooks on Cursor

Version: 1.2.4
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T16:53:59.659Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Same issue. Any workarounds?

Same issue, super disruptive to Jupyter workflows

Version: 1.3.0 (Universal)
VSCode Version: 1.99.3
Commit: 410000a83355c025daba0c6156955bf08687d080
Date: 2025-07-23T05:46:59.221Z (11 hrs ago)
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.1.0

cc @ravirahman

Same issue here, guys, jupyter workflow is completely broken by this, please fix asap

Hi all, thanks for sharing this issue. We are looking into it.

Still present in 1.3.4
Seriously guys, is it that hard to fix?

Having the same issue. As a brand new user to cursor, I am not very impressed in finding a bug within 2 hours of starting to use it.

Same problem here! It’s very annoying to code with this bug

Sorry about this - we have a fix complete but it was not included in today’s release.

Still present in today’s release 1.3.7
When can we expect the fix to come out??