Hi,
I have recently updated to what I think is your latest release (11.2.20112.45) and it seems to have introduced some weird behaviour into the dropdowns.
1. If you click into a dropdown and open the popup, but don't select any items, close the popup and then tab to the next field, the dropdown selects the first item in the list.
2. You can never select anything other than the first record in the dropdown. Everytime I select something different it reverts back to the previous selection when tabbing out.
I even encountered this behaviour in a sample application that you guys sent me after upgrading it to the latest release.
Is there something I need to do to stop this behaviour occuring?
Thanks.
Hi Calsy,
there is new release(11.2.20112.74) which should contain the fix for the issue you've described. Could you check if if the fix in the newest release fully covers the issues you have found.
Regards,
Hi Konstantin,
Unfortunately I still seem to be experiencing the same issues. I have attached a sample application that is showing the behaviour.
Steps to reproduce:Issue 1:- Click on the dropdown button to open the popup.- Without selecting anything, click on the dropdown button to close the popup.- Click on the Textbox.- Item 1 is selected in the dropdown.
Issue 2:- Select Item 1 from the dropdown.- Click on the Textbox.- Select Item 2 from the dropdown.- Click on the Textbox.- Item 1 is reselected in the dropdown.Thanks.
I've just been doing some more testing and the issue only presents itself when you set the CustomValueEnteredAction to Add, as it is in my sample project.
I've managed to reproduce both issues and submitted internal bug items for them(although I think the root cause is the same) the bug items are #100843(Issue 1) and #100844(Issue 2). I've also created a support case on your behalf - CAS-83486-Q34PZF so you could be notified when the fixes are released.
Thank you for taking the time to report these issues and in a such clear manner.
Has this been fixed? I may have to go back to just the combo box unless this has been fixed. It makes this control unusable.
No it has just been reported and will be fixed in the next Service Release which will will be out in the beginning of March.
As Calsy has mentioned the problem occurs only when the CustomValueEnteredAction is set to "Add".
I'll ask our Developer Support team to create a support case for this and provide any further assistance on the matter.