Hi Jesse, Thanks for suggestion about using dropdownDescriptorSelector! However, I was using an example from ui-samples-plugin, it's almost an exact replica. So I guess this sample plugin should be updated as well.
Do you have a more interactive community, like an IRC chat? I'd like to invest into enhancing UI controls and have a few suggestions regarding UI testing, Jelly controls and - what's most important - user documentation. What's the best way to discuss them and start implementing if considered needed? Regards, Kirill. вторник, 10 ноября 2015 г., 14:48:06 UTC пользователь Jesse Glick написал: > > On Tue, Oct 27, 2015 at 11:34 AM, Kirill <yam...@gmail.com <javascript:>> > wrote: > > what about case when there are two <f:dropdownList/> elements? > > First of all, you should be using `f:dropdownDescriptorSelector` for > data binding, rather than a raw `f:dropdownList`. > > Probably what you are asking for is not possible without either > patching Jenkins core, or producing your own form controls from > scratch. `f:select` computes its values dynamically, using an adjunct > (`select.js`). You would need a hybrid. > > Just one of many inconsistencies and missing features in the stock > form controls, I am afraid. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/376ec49f-3f37-4565-93da-81b58d5f63a4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
