The keyboard interaction feels strange on the unified search input. Anytime I am in a long textarea element I often use ⌘ + shift + ↓ or ⌘ + shift + ↑ to jump to the start or end of the text. In this case, ⌘ + shift + ↑ works fine but ⌘ + shift + ↓ does nothing to the location of the cursor in the textarea content.
Steps to reproduce
Open discover with any sample dataset
Type a long query in the KQL search bar
With the text area open, try to navigate the text of the input using keyboard ↑, →, ↓ & ← arrows.
Notice when going down, the cursor is not properly moved in the text area input. Rather the down controls the focused option from the list.
Actual Result
The down arrow always controls the selection of the hovered item in the dropdown.
Expected Result
The down arrow traverses the text input until it is at the bottom at which point it could break away to control the selection from a list of options.
Kibana Version:
8.16 and before
Browser:
Chrome -- Version 129.0.6668.90 (Official Build) (arm64)
The keyboard interaction feels strange on the unified search input. Anytime I am in a long
textarea
element I often use ⌘ + shift + ↓ or ⌘ + shift + ↑ to jump to the start or end of the text. In this case, ⌘ + shift + ↑ works fine but ⌘ + shift + ↓ does nothing to the location of the cursor in thetextarea
content.Steps to reproduce
https://github.com/user-attachments/assets/806f4497-a96a-457d-a79b-916fabe97c73
Actual Result The down arrow always controls the selection of the hovered item in the dropdown.
Expected Result The down arrow traverses the text input until it is at the bottom at which point it could break away to control the selection from a list of options.
Kibana Version:
8.16
and beforeBrowser:
Chrome --
Version 129.0.6668.90 (Official Build) (arm64)