Duncan McLean wrote:
Hi Jason
Thanks for drawing my attention to this...
Are there any workarounds, or will have to choose between
ajax-enabling our forms or having validation-errors work, for the time
being?
An optional "Turn off ajax" attribute per widget [1]. Please note, this
patches
Hi Jason
Thanks for drawing my attention to this...
Are there any workarounds, or will have to choose between ajax-enabling
our forms or having validation-errors work, for the time being?
Thanks
Duncan
Jason Johnston wrote:
We have a form that has several fields that are enabled/disabled t
> We have a form that has several fields that are enabled/disabled through
> on-change events in the form. This works fine, and with Ajax too...
>
> We also have validation which includes a list of "validation-errors"
> which displays all errors in the form at the top of the form (in this
> case).
Hi
We have a form that has several fields that are enabled/disabled through
on-change events in the form. This works fine, and with Ajax too...
We also have validation which includes a list of "validation-errors"
which displays all errors in the form at the top of the form (in this case).
The ma
