Since we’re bug reporting anyway, same issue is for when clicking a ui elements and then it’s placed inside the chat window, the data pop up of the elements also blocks input. Happens so many times a day..
Hey, this is a known issue that was fixed in recent versions of Cursor.
Try updating Cursor to the latest version. The fix was released in early January.
If the issue still happens after updating, please share your Cursor version (Help > About) and a new screenshot, and we’ll check further.
tihs is from
Version: 2.4.0-pre.45.patch.0
VSCode Version: 1.105.1
Commit: 0dbc25609bb70f13e062f5cb7f6e66e7d1d109f0
Date: 2026-01-17T22:43:13.243Z
Build Type: Stable
Release Track: Nightly
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0
1 Like
Still seeing it
Version: 2.4.7
VSCode Version: 1.105.1
Commit: ca0f9bf806f235ea014a22712cbcbf5e88ca77e0
Date: 2026-01-20T20:52:38.077Z
Build Type: Stable
Release Track: Early Access
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0
The chat input window is like the MOST important part of your whole UI/UX. Millions and millions of daily interactions. Getting this ABSOLUTE pixel perfect is REALLY REALLY worth the effort. Please invest in this. Daily annoyances stack up if you get them 100+ times a day.
Some more feedback: the UI editor is amazing. It lets you be some much more precise when building UI’s. But what is a bit tedious; if you are in ‘select UI elements in DOM’ you can not quickly override this mode when you do want to actually perform a click on a UI element instead of placing the info in the chat window.
Holding some kind of shortkey like shift, ctrl, or cmd to temporarily override the DOM selector would be great feature and save lot of time while doing UI work.
This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.