RodrigoK wrote:Can eValid confirm that active processing of an input field is correctly trapped by the local JavaScript logic?
The basic answer to this is "yes".
But the variations on how to do it depend on how the input field is being processed. This in turn varies based on the JavaScript coding that handles that input field. There are as many ways to do this - it seems, sometimes -- as there are programmers willing to write the JavaScript. In other words, a lot of variations.
To find out if a field is actually "active," that is, if it is changing dynamically, you need to have a "before" and an "after" value for the input field. Once you have these you can use the set of commands that do AJAX synchronization to "validate and synchronize" on first one, and then the other value.
You can read about two of these key eValid commands here:
Playback Synchronization on DOM Element--eValid Support