text input in the chat window unintuitive and hard to use for longer texts #5662
Description
Feature Description
I would really like you to have another look at the text input in the chat window (bottom right corner of the flow interface) , as it is hard to work with especially for longer user-input.
Feature Category
UI/UX Improvement
Problem Statement
There are a few annoyances that are sort of acceptable and one can get used to:
- it's hard to type a longer input (>3 lines) in the chat box in the ordinary interface (right bottom corner) because the box is not high enough to get an oversight of what you type (only contains 3,5 short lines).
- For someone used to type multiline inputs, there is a problem in that enter button triggers committing the input (as it is unfortunately in some chatbots) whereas the user only intended to start a new line. This is annoying but user can train to use shift enter.
- But the most irritating I find the way the arrow up and down buttons work when the cursor is in the input-box. Instead of the cursor moving a line up or down in what the user has typed, as is the behaviour in 99,9% of all text input boxes, this window will switch contents completely to preset answers (probably for the Human Input Node): Proceed or Reject. A lot of the time there is no going back from that: correcting with the reverse direction arrow button mostly does NOT give the user the text they were typing back, but some other old entry. Thet text the user was typing just vanished for good, without any warning. This can mean minutes are lost and everything needs to be redone.
Proposed Solution
- Disable the switch to Proceed/Reject, and make arrow buttons work like any other (like the one I am typing in right now).
- Make the box a little bit higher (or resizable)
- optionally: make enter button not trigger a commit or make that behaviour adjustable in settings
Mockups or References
No response
Additional Context
No response