Hi, The new code registers listeners with jQuery's on() method which uses internally addEventListener() (IE9 and others) and attachEvent() (IE8 and less). So you need to execute your JS code after Wicket's. Wicket executes its bindings when the DOM is ready, so you must be careful that your Mootools code is run after Wicket's. Better try with a simple app and see how it behaves.
On Mon, Jan 30, 2012 at 5:49 PM, Thomas Götz <[email protected]> wrote: > Just a thought about the upcoming changes to Wicket's Javascript event > registration mechanism in Wicket 6.0 (instead of inline JS events): > > we have several Behaviors that provide Javascript in which we register to JS > events, e.g. 'onblur'. Now I have a Component that additionally has an > AjaxEventBehavior("onblur"). Currently, the Behaviors that registered to > 'onblur' are guaranteed to execute before the inline 'onblur' event (provided > by the AjaxEventBehavior). Could this be a problem with Wicket 6.0? Meaning: > will it still be possible to provide additional Behaviors that register JS > events that execute *before* any event behavior already registered to some > Component? Or how will Wicket's JS event mechanism figure out the order of > Behaviors? > > Cheers, > -Tom > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
