[Dropdown] What to do with it now that we have the DS Select implemented?

[meissadia]

A searchable select seems like a very useful component to have, and is already built, but we also don't want DSR consumers to get confused about which component is CFPB approved.

• Create a new category for non-CFPB DS components?
• Leave the component in but don't list it in Storyboook?

[natalia-fitzgerald]

@meissadia
I discussed this with @billhimmelsbach in the context of a separate discussion that we were having about the Point of contact form (state Select).

In their Create a user profile pattern - address the USWDS recommends:

Avoid dropdowns that require long scrolling. If possible, let users type their state or territories’ abbreviation when they reach the state dropdown menu, instead of having to scroll and select."

In the USWDS Create a user profile pattern - address pattern they use the Combo box component (instead of Select). The combo box component allows for filtering of data in the list when a user types in the field. The USWDS recommends this approach for when there are more than 15 choices in a drop-down list.

The Combo box seems to have some overlap with our original "Dropdown" component. Although we we plan to use the standard Select as the state selector for MVP, we would like to hold on to this code in the event that we decide to create a Combo box component in the future. As a next step can we remove the "Dropdown" component from being visible in the Storybook library but save the code AND rename any references within that code to Combo box (instead of Dropdown)?

If we do decide to pick up this code in the future there will still be quite a bit of styling work too capture our styling, however. This component never reached alignment with our styling. So, I do wonder whether we will want to save all of the code or just the part that adds the filtering functionality. We can discuss this next week if you'd prefer.