Open LasseRosenow opened 1 year ago
Appreciate the suggestions and agree that they're sensible and consistent. We did struggle to find an appropriate name for what had been called "ComboBox". Eventually we settled on DropdownMenu because that's what the Material Design team thought it should be called and because it's short. Naming is definitely hard, more so when you're adding a name to an ecosystem of names that's been evolving for 5+ years.
@HansMuller There's also PopupMenuButton
/DropdownButton
. The m3 guidelines effectively describe all three of these as a single component. I think it would be a lot simpler to handle the particularities (how it's opened, whether it can be filtered, searched, etc.) by parameters on a single widget, rather than have separate and different API in 3+ widgets.
This issue is missing a priority label. Please set a priority label when adding the triaged-design
label.
Now that the new
DropDownMenu
widget landet, I am a bit surprised by its name choice. It seems to be inspired by the oldDropDownButton
widget, but it does not really make sense in my mind.PopupMenuButton
DropDownMenu
What I find confusing is that
Popup
bsDropDown
... Is both kinda the same. But then why doesDropDown
mean textfield as trigger?Use case
Confusing naming of widgets is a problem for new developers. So having more obvious names that align with the spec is good.
Proposal
In general I think the "popup" is a word that does not appear in the material spec. So why not just remove it? And then align the 2 widgets to each other: (This would be breaking, but could be done by just introducing new widgets):
MenuButton
MenuTextField
MenuTextField.autocomplete