Skip to content
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

[Feature Request]: ComboBox offers no suitable affordance to indicate values entered by typing will not be accepted #16498

Open
1 task done
Tracked by #16102
grahamharper opened this issue May 17, 2024 · 2 comments

Comments

@grahamharper
Copy link

grahamharper commented May 17, 2024

The problem

ComboBox offers no suitable affordance to indicate values entered by typing will not be accepted.

Currently when you type into ComboBox, then blur the input, the entered text is cleared and it reverts to the previous value/state. I believe the intention of this was to indicate to the user that custom text was not allowed.

Now imagine a scenario where the ComboBox has a default selection. User enters some text that exactly matches another option in the list, but instead of moving focus away from the field—because maybe there are no more inputs in the form—they use their mouse to click the Submit button.

Combobox will blur, clear their entered text and revert to the default selection. This all happens faster than the user can perceive. Form submission validation won't catch it because the input has a valid selection, but nonetheless, the user has submitted a selection they did not intend.

Now, why might the user type text as their value instead of explicitly selecting an option from the list? Well, maybe they find that faster, maybe they're pasting text, using autofill, but also the input does not indicate in any way that values entered by typing will not be accepted.

There is no affordance to users when allowCustomValue is true or false.

I'va also added this as a comment on #16307

The solution

For example, utilising more of a filterable select pattern which separates the UI showing the current selection from the input used to filter/search the options.

  • The current selection is shown in the button that triggers the popup.
  • The search/filter input is inside the popup.
  • When the popup is closed, the search/filter text is discarded and the selection remains.

Examples

Here are two examples of this:

Chosen
image

GitHub
image 2

In these examples the state of the current selection is clearly distinguished from the search/filter text. A user is less likely to think that the text they have entered will be accepted as a value for the field.

Application/PAL

No response

Business priority

None

Available extra resources

No response

Code of Conduct

Copy link
Contributor

Thank you for submitting a feature request. Your proposal is open and will soon be triaged by the Carbon team.

If your proposal is accepted and the Carbon team has bandwidth they will take on the issue, or else request you or other volunteers from the community to work on this issue.

@sstrubberg
Copy link
Member

Check with @benjamin-kurien regarding this work being a dupe of the work-stream that he created as a follow up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants