Quick Edit Panel input reversed on ABNT2 Layout (Ticket T-C19351)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am experiencing a critical input bug where the Quick Edit panel (Ctrl+K) types text completely backwards when using a Brazilian Portuguese ABNT2 keyboard layout. Instead of advancing normally from left to right, the text cursor position fails to advance, pushing previously typed characters to the right and mimicking an incorrect Right-to-Left (RTL) behavior (e.g., typing “test” results in “tset”)

Steps to Reproduce

  1. Open Cursor and focus on any open file;
  2. Open the Quick Edit panel using the shortcut Ctrl+K;
  3. Start typing any word or prompt using a pt-BR/ABNT2 keyboard layout;
  4. Observe the input field rendering the text in reverse.

Expected Behavior

The text should render and advance normally from left to right as the user types

Operating System

Windows 10/11

Version Information

Cursor Version: 3.2.11

OS: Windows 11 Pro (Build 10.0.26200)

Additional Information

  • Machine: Acer Nitro AN515-43 (BIOS: V1.12, RAM: ~30GB)
  • Hardware Layout: ABNT2 (Layout ID: 00010416)

I have already reported this via support email (Ticket T-C19351), but I wanted to share it here to open up a discussion, see if anyone else in the community is facing this same issue, and maybe figure out a temporary workaround or solution together

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey, this is a known bug with Ctrl+K Quick Edit and we’re already tracking it. Based on past reports, the trigger is usually split editor panes or a detached window. After you change focus in the Lexical editor, the cursor stops moving forward and each new character gets stuck on the left. The layout itself usually isn’t the cause, but ABNT2 might have happened at the same time as this state.

Workaround for now: Ctrl+Shift+P → Developer: Reload Window. After the reload, typing in Ctrl+K should work normally until the same state happens again.

A couple questions so I can file a more precise report:

  • Are you using split panes in the editor or a detached window (for example, chat or the editor in a separate window) when this happens?
  • If you open Cursor with a single pane, no splits, and no detached windows, can you still reproduce it?

If it reproduces only with ABNT2 and without splits or detached windows, that would be a useful separate data point. I can’t share an ETA for a fix yet, but I’ll attach your report to the existing issue.

Related threads: