Okay, sorry,
this wasn't really a Wicket-Problem but an IE-Problem. The Button in my application is actually a div and IE has problems to focus() divs (sometimes), so that when clicking the div, the focus is not removed from the text field and no onchange-event is fired.
I managed it by giving the button div a tabIndex="0" attribute on in its onclick I call this.focus(). Then it works (even in IE).
cretzel wrote:
Hi,
I'm having a problem regarding JavaScript/Ajax and I'm not sure if it's actually related to Wicket.
I've got a Button and a TextField within a Form. The TextField uses an AjaxUpdatingBehavior for validation, which is fired "onchange". The Button submits the form via Ajax "onclick". In my case, sometimes the onchange event occurs after the onclick event (on the clientside), which causes problems. This is only a problem in IE(6) and not in FF. In FF the onchange event always occurs before the onclick event. And even in IE in simple examples I could never get the onchange event to occur after the onclick. So my question is, if this could have something to do with wicket's ajax JavaScript.
Regards
