|
Hello, there have been several discussions about loosing
click events in case the user is editing some text input field with focus
listener or an updateable table cell. The advice to use asynchronous event
delivery modes was always accompanied by the warning that this might result in
undesirable effects because the target element for the click (e.g. the submit button
of a form) might be disabled by the focus lost or table update event. I am now
wondering if thisis the only complication. Is it possible that the secondary
(asynchronous) click event on the submit button overtakes the update in the
input field or table cell and that the submitted form is then not evaluated correctly? In other words, is it guaranteed that the secondary event
is processed on the server side after
the first event has been processed on the server side completely – i.e. the
client does not block – but the server still does. Cheers Stefan |
- [ULC-developer] Setting event delivery to asynchronous mode ... Stefan Thomas
