-
Notifications
You must be signed in to change notification settings - Fork 841
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EuiCombobox][COGNITION]: Combo boxes should open on user interaction instead of focus
event
#5951
Comments
👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment. |
This issue should be addressed following dedicated user research. |
👋 Hi there - this issue hasn't had any activity in 6 months. If the EUI team has not explicitly expressed that this is something on our roadmap, it's unlikely that we'll pick this issue up. We would sincerely appreciate a PR/community contribution if this is something that matters to you! If not, and there is no further activity on this issue for another 6 months (i.e. it's stale for over a year), the issue will be auto-closed. |
❌ Per our previous message, this issue is auto-closing after having been open and inactive for a year. If you strongly feel this is still a high-priority issue, or are interested in contributing, please leave a comment or open a new issue linking to this one for context. |
We plan to address this when we work on #2841 |
Description
A customer raised this as an issue with our sitewide search in Kibana. When users click or keypress navigate to our sitewide search, the combobox opens automatically. This is an issue with Success Criterion 3.2.1: On Focus because we are making a significant change of page context.
Suggested change
Can we explore changing the
listbox
show event to listen for keypresses likeDOWN_ARROW
or letters when users start typing? This might be a breaking change item, so happy to discuss further.Guidance
The text was updated successfully, but these errors were encountered: