From a perspective of an autocomplete, we are looking for something which is more intuitive(like a textbox) and does not involve a button to open the dropdown, The above is a data-grid encapsulated in a modal, and there are too many actions the user needs to perform to select something, An autocomplete should be pretty intuitive like the combobox mentioned above (but the example 1 or 2 in this-> https://www.w3.org/TR/wai-aria-practices/examples/combobox/aria1.1pattern/listbox-combo.html) without the dropdown button

The main problem with having it simply as a list of building blocks is consistency. Given that this is going to be used across different products and technologies it would be beneficial to limit the possibilities. Hide some of the logic needed for this kind of component to work.

If we leave it as is each time someone builds something similar they will have to answer the same questions:

• what are the size restrictions,
• how to properly position it and what kind of trigger element to use,
• how should the selection behave - only a checkbox or additional styles for rows,
• should the dropdown close on click outside,
• how to show if no elements match the search,

They might not be big issues alone but might cause a lot of confusion when implemented in different ways in different places. We created such a component in our application and had to decide on the behavior. It would be a lot easier if we had the possibility to use a component that works the way the UI and UX designers want.

Also, there might be incompatibilities between different components. Like e.g. we used a list component that was clearing the selected items each time we filtered the elements. Or not being able to use a select component as a trigger.

will be handled in https://jira.vonage.com/browse/VIV-654

related request by UP require virtual scrolling to handle large length items

To me it seems that this should just be the select component, with extra optional parts like the search box, header/footer etc.
A feature not mentioned here that might be useful is some way to divide the items into categories (the example I have in mind is extensions categories in VBC, like call-group, call-queue, regular extension, VR, etc.).
There should be a way to see for each item which category it is, and also search by category.
Another thing which I assume is included but didn't see mentioned is that it must have a virtual scroll, o/w it will be useless for large amounts of data.

Another use case requested from AI

Adding the selected items from the dropdown to a chip-set in the input field.

(proposed components architecture)

Follow https://www.w3.org/TR/wai-aria-practices-1.2/examples/combobox/combobox-select-only.html