Description of problem: dropdown fields marked as required are not letting a custom dialog validate even with values selected Version-Release number of selected component (if applicable): 5.9.0.22 How reproducible: all the time Steps to Reproduce: 1. create a simple dialog with no automation and a couple drpobox fields allowing only one value to be selected 2. try to use the dialog, selecting every value then going back to the first value and making another selection Actual results: the dialog does not validate Expected results: the dialog validates as expected Additional info: attaching privately information regarding this dialog from the customer case
using "required" on a dropbox will make the form impossible to validate no matter what.
Could you retest this on a Updated gaprindashvili appliance and validate whether it works for you?
(In reply to Chris Hale from comment #6) > Could you retest this on a Updated gaprindashvili appliance and validate > whether it works for you? I don't have one ready, if you can share one I can do the test.
Not able to recreate on 5.9.2.0.20180320210136_355c506 and 5.9.1.1.20180321221247_67fd99d
See comment 8, can you please retest.
Felix, please see comment 10
I do not have a 5.9.1 appliance ready for testing and as things stand will not be able to test until the errata is actually released.