On Wed, Aug 26, 2020 at 7:27 AM Christopher Dodunski (Tapestry) < chrisfromtapes...@christopher.net.nz> wrote:
> Thanks Thiago. > My pleasure to help! > I guess it's something worth considering in the future - updating > BeanEditor and related components to better leverage HTML5 features. > Which ones, specifically? And Tapestry form field components do handle disabled="true" correctly as far as I remember, completely ignoring disabled components when processing the form submission, so I don't think your workaround described below is needed. What HTML5 features do you mean? > > A workaround in my case was to have SelectModelFactory reduce the number > of selectable elements down to one, making selecting something different > impossible. The fields of interest are synthetic properties added to > the BeanModel, so this workaround was possible. > > Regards, > > Chris Dodunski. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Thiago
