Answered

ComboBox Chevron Disappears on drop down.

(0) Share

Report

Posted on by PowerAppsJunkie

151

I'm assuming this is default behavior as this has been my experience since using the combo-box control but I thought I'd ask. It's honestly a horrible experience in the UX for users and in MS native apps etc...clearly is not the behavior so extremely curious why this is best practice for use in Power Apps. The experience is when you click the drop-down in a combo-box you immediately lose the chevron drop down to collapse your choices and are forced to close the combo-box in an unnatural way. Using the drop-down control you get the chevron that stays. I know the modern control is much better with this functionality but the properties for the control are still extremely limiting.

Combo-Box collapsed showing chevron

Combo-Box expanded - No chevron to collapse

Drop Down Control shows chevron even when expanded

Categories:

Building Power Apps

All responses (2)

Answers (1)

Sort by

Verified answer

v-yueyun-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi , @PowerAppsJunkie
According to your description, the Combo box's chevron will disappear when expanded.
It is by design in Power Apps and it also the same in my side :
When we click the chevron, the Combo box will expand , and we can tap on the blank part of the screen to return the Combo box to its initial state. And now it have no configuration to set this action.
Because the Combo box can be searched. But DropDown doesn't support it.
And you can refer to this video to see the difference between DropDown and Combo Box Control:
DropDown Vs Combobox in Power Apps - YouTube

If you would like this feature to be added in PowerApps, please submit an idea to PowerApps Ideas Forum:
https://powerusers.microsoft.com/t5/PowerApps-Ideas/idb-p/PowerAppsIdeas

Best Regards,
Yueyun Zhang
PowerAppsJunkie 151 on at

Like
a
(0)

Report
Copy link

Link copied!

I just wanted to be sure it was by design. It's a terrible design but it does seem to be addressed in the Modern version of the control but that version is still very lacking as far as property parity with the older control version. So hopefully this will continue to improve.

As many of these UX elements follow Fluent 2 UI you'll notice this is in this example and it is more in line with what the modern combo-box is.

https://fluent2.microsoft.design/components/web/react/combobox/usage