I would just call it what it is - like "ComboBox"

i just dont like dropdown tbh

I wouldn't tack on the dropdown

whats "wrong" with "ItemSelector"?

MenuItemSelector, ListItemSelector (could alias it as DropDown eventually), etc

selector i think of these:

eg:

xml
        <item-selector width="150" itemSelectionEvent="menuselected">
            <menu>
                <menu-item text="Item 1" />
                <menu-item text="Item 2" />
                <menu-item text="Item 3" />
                <menu-separator />
                <menu text="Menu A">
                    <menu-item text="Item 1A" />
                    <menu-item text="Item 2A" />
                    <menu-item text="Item 3A" />
                </menu>
                <menu-separator />
                <menu-item text="Item 4" />
                <menu-item text="Item 5" />
                <menu-item text="Item 6" />
            </menu>
        </item-selector>

you mean lists?

i mean the behaviour to expect from using the component

a selector != a drop down

picker?

ItemPicker?

A picker i think is more "free form", a drop down is typically a vertical list box that expands from a source component and you select it

the reason im kinda trying to avoid "dropdown" is because of that, because on mobile (or with a flag), i can change all the behaviours of the "pickers" (or whatever)

ie, they can show a dialog, or slide the "panel" up from the bottom, etc, etc

then i think this is a case of going against convention, i guess

like "TimePicker" can show times in a dropdown, or, on mobile, could show a panel in the bottom with the screen with the same controls to pick a time

im starting to feel like "picker" feels like the best option?

because i don't think it is "tech culturally" intuitive to group these behaviours under a single umbrella

ListItemPicker, TimePicker, DatePicker, ColourPicker, etc... arent they grouped?

Picker may be the best option i think with that route

they all involve the user "picking" something... no?

Well it would get weird if you set that standard and then get to "DropDownPicker" 😄

but it wouldnt be dropdown picker... it would be "ListItemPicker"

Ohh i see

possible side effect there may be people asking how to do a dropdown and miss that association

ie, "what are picking"

but I do agree here

it's just not the conventional description

i could certainly alias, "typedef DropDown = ListItemPicker"