Arrow keys, Home, and End keys not working in "Save as" dashboard title input

[chkang-idk2]

Bug description

1. Open any dashboard (either in View or Edit mode).

2. Click on the triple-dot menu (top right) and select "Save as".

3. Try to move the cursor within the "Dashboard name" input field using the Left/Right arrow keys.

4. Try to jump to the start or end of the text using the Home or End keys.

5. Observe that the cursor does not move, although typing alphanumeric characters works fine.

Screenshots/recordings

No response

Superset version

6.0.0

Python version

3.11

Node version

18 or greater

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[chkang-idk2]

The Theme name input box in 'Theme & CSS' looks the same too.

[dosubot]

Both the "Save as" dashboard title input and the Theme name input in the "Theme & CSS" modal use the same standard Input component, with no custom logic that should block arrow keys or Home/End navigation—they should behave like normal text fields. However, there are reports that keyboard input issues (like navigation keys or certain characters not working) are affecting multiple input fields in Superset 6.x, likely due to a shared frontend input or validation layer rather than the individual input components themselves (source).

Just to clarify, are you seeing the same keyboard navigation issue (arrow keys, Home, End not working) in the Theme name input box, or was your comment only about the visual similarity? If the issue is present, it may be part of this broader input handling problem.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[chkang-idk2]

@dosu
The same thing is happening.

[dosubot]

Thanks for confirming—this means the keyboard navigation issue is affecting multiple input fields, not just one modal. Both the "Save as" dashboard title and the Theme name input use standard Ant Design Input components, and there’s no custom logic in these modals that would block arrow keys or Home/End navigation. This points to a broader frontend input handling problem, possibly from a shared/global handler or a higher-level bug, not the individual components themselves.

There aren’t any documented fixes or workarounds for this in the codebase or issue tracker as of now. If you’re able, it could help to check for any global event listeners or browser console errors, or try a different browser to help isolate the cause. Let me know if you want to dig deeper into possible global input handling or need help narrowing it down further.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}