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
Instead of using the <select> tag to setup the options have another API "path" that would make use of custom elements. This would allow just about any markup in the options (and the groups).
To finish this feature there are some remaining issues to work though:
In the selected value part of input field, what do we show in single select and in multi select? Do we just show the select value? Or a label?
When we're filtering down the options by typing, what text is the filter working off of? Does
(should) this feature even work if a <much-select>'s options are being rendered this way?
Instead of using the
<select>
tag to setup the options have another API "path" that would make use of custom elements. This would allow just about any markup in the options (and the groups).So things could look something like:
I think things will work out better if each option has it's own unique slot.
The text was updated successfully, but these errors were encountered: