[Discover-Next][UX] Query editor keyboard actions #7039
Open
Description
Description
Implement the behavior of keyboard interactions with the query editor. For example, for the default experience (query string input) when the user hits the {enter}
key then the query is fired. But the query editor supports multiline'd queries. Currently, pressing {enter}
key moves the cursor to the next line. But the learned reaction of being able to press the {enter}
key and the request not firing can be unlearned but then the interaction on another page still fires the request on {enter}
Requirements
- UX questions:
- Are we okay with the behavior in the description (enter firing the request on different apps like dashboards and visualizations, but new lines for query editor)?
- Explicit list of other keyboard actions?
- Example from the default experience
- Any difference in behaviors between the editor and input accounted for
- Any keyboard interactions for expansion/collapse feature? [Discover-Next][UI] Query editor can be collapsed #7038
- Implement