Hello,
I am in the process of refactoring my application using components. I have come across something that appears to be a bug with components but I cannot find anyone else reporting this behavior.
Set up:
I have a component containing 2 elements, a combo box and a label:
I have placed the component on a screen and enabled searching. The act of typing or selecting an item causes the combo box to revert to the non-searching state. below is a demonstration of this using blank rows:
Any behavior applied to the drop down makes it behave like the example. I've tried the following:
- using a collection directly within the dropdown.
- using a collection at the component level with an input called 'dropdownitems' and using Parent.dropdownitems.
- I've tried changing multi-select and search to true and false. I've also used component inputs.
- I've tried this with collections and directly from data sources.
- I've tried with and without default values.
Observations:
- when searching, each keystroke seems to cause this unless you type very quickly. It seems like any change to the items using the search makes it disappear.
- When you search, the search text and results are present when you click the combo box.
- Using the same data source with a combo box OUTSIDE a component works perfectly as expected.
Anyone have any ideas why this is happening? this effectively makes combobox searching useless which is unfortunate because this is one of the controls that would be best suited to be a component.
