You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TLDR; After submitting a question and getting an answer in the ai-chat, the input field should have focus, so a user can input a follow-up question right away.
It seems, after submitting a question in the ai-chat, the focus is not with the input field an all cases.
At first glance, it seems that the behaviour described above happens (almost) all the time. I believe whenever there is an immediate response to a particular question, the cursor stays in the input field and you can type a follow-up question without having to focus the input field again first.
On the other hand, whenever the question takes a request to the backend to be answered, the focus leaves the input field. Hence, after that you have to select the input field again using the TAB-key to input a follow-up question.
In short, all queries would start in the prompt field and return to the prompt field.
However, one must not forget, that responses must be announced by screen readers, and the user must have the possibility to navigate to particular elements of the response, for example if there are links with the response, a user might want to visit those.
Reproduction/example
non
Steps to reproduce
leverage ai-chat component
force an immediate response, the focus stays in the input field
force a response, that involves a backend request, the focus goes away.
Suggested Severity
Severity 3 = User can complete task, and/or has a workaround within the user experience of a given component.
Browser
Chrome, Safari, Firefox
Package version
0.14.1-canary.347
React version
^1.66.0
Description
TLDR; After submitting a question and getting an answer in the ai-chat, the input field should have focus, so a user can input a follow-up question right away.
It seems, after submitting a question in the ai-chat, the focus is not with the input field an all cases.
At first glance, it seems that the behaviour described above happens (almost) all the time. I believe whenever there is an immediate response to a particular question, the cursor stays in the input field and you can type a follow-up question without having to focus the input field again first.
On the other hand, whenever the question takes a request to the backend to be answered, the focus leaves the input field. Hence, after that you have to select the input field again using the TAB-key to input a follow-up question.
In short, all queries would start in the prompt field and return to the prompt field.
However, one must not forget, that responses must be announced by screen readers, and the user must have the possibility to navigate to particular elements of the response, for example if there are links with the response, a user might want to visit those.
Reproduction/example
non
Steps to reproduce
Suggested Severity
Severity 3 = User can complete task, and/or has a workaround within the user experience of a given component.
Application/PAL
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: