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
