Migration issue: fire AjaxFormComponentUpdatingBehavior(change) by Javascript the Wicket 6 way?

2013-02-22 Thread Martin Dietze
I understand that with Wicket 6 the event handlers are no longer inline, thus calling input.onchange() will no longer work. But what do I now do instead? I have hand-written inputs which rely on onchange() being called via Javascript after user interaction. So what do I have to call inside my JS

Re: Migration issue: fire AjaxFormComponentUpdatingBehavior(change) by Javascript the Wicket 6 way?

2013-02-22 Thread Martin Grigorov
jQuery(selector).triggerHandler('change') On Fri, Feb 22, 2013 at 11:36 AM, Martin Dietze d...@fh-wedel.de wrote: I understand that with Wicket 6 the event handlers are no longer inline, thus calling input.onchange() will no longer work. But what do I now do instead? I have hand-written

Re: Migration issue: fire AjaxFormComponentUpdatingBehavior(change) by Javascript the Wicket 6 way?

2013-02-22 Thread Ernesto Reinaldo Barreiro
$(#componentid').trigger('change');? On Fri, Feb 22, 2013 at 10:36 AM, Martin Dietze d...@fh-wedel.de wrote: I understand that with Wicket 6 the event handlers are no longer inline, thus calling input.onchange() will no longer work. But what do I now do instead? I have hand-written inputs