NEXT: InputChips

[Sarenor]

[!WARNING] This issue is a work in progress.

This will act as a hub to centralize this information.

Maintainer Requests

The following requests are coming straight from the Skeleton team. These are highly likely be implemented:

• After InputChips, Autocomplete & Popups are all implemented, we should make sure that the documentation combining all 3 is as explicit as possible, since that was an area people really struggled with.
• We also need to check Svelte Reactivity carefully.
• https://github.com/skeletonlabs/skeleton/issues/2039
• Never embed <form> elements; use the new mobile-friendly keydown method instead (REPL)

Community Requests

The following requests have come from the community and are under consideration:

• https://github.com/skeletonlabs/skeleton/issues/1665
• https://github.com/skeletonlabs/skeleton/issues/2577
• From Discord: each data item should be an object in case of dupes (ex: {id: 0, label: "foo"})

Feedback

If you have additional updates or requests for this feature, please do so in the comments section below.

[TazorDE]

I just noticed that the current iteration of Input Chips doesn't support the input groups style of adding leading and trailing icons, text, or similar. Or at least I couldn't find it. In my opinion this is something we should consider adding support for, as it greatly improves the possible uses of the component.

[endigo9740]

The problem is the height. It tends to be at least 2x tall as any other component, similar to a textarea. Not saying we can't support it, just that it would be a bit more of a challenge.