search

CodeBeamOrg / CodeBeam.MudBlazor.Extensions

Useful third party extension components for MudBlazor, from the contributors.
https://mudextensions.codebeam.org/
MIT License
369 stars 62 forks source link

(Question) Why use ChipSet inside components? #279

Open Geccoka opened 9 months ago

Geccoka commented 9 months ago

It's not a bug, more like a question to the authors.

Why use MudChipSet in components that enables multiselection? Why not use just MudChips?

The MudChipSet has a feature that the individual chips can be selected, and the selection causes that the chip changes its variant, eg. from Text to Filled or the other way around. If you use the MudChipSet alone this selection function with the visuals is of course a good feature, but inside a component that allows multiselection selecting the individual chips make no sense and and makes a visual interference if somebody clicks one. The MudChip also has a Close function that allows the parent component to remove individual chips.

So i can see only drawbacks using MudChipSets rather than individual MudChips.

This looks wierd IMO: kép

What is your opinion?

mckaragoz commented 9 months ago

@Geccoka MudChipSet also provides that chips can be closed individually etc. has lots of mechanism. I agree that the click behavior is not correct inside the input, i think we should change MudChipset design itself, not MudSelectExtended