Jeremy, I know this is true with real domready event, but in my experience wicket domready is somehow more intelligent that it knows how to behave in ajax requests. At least in my experience using jquery domready $(document).ready will not work in ajax requests but wicket.event-based domready will work perfect in ajax refresh also. So I guess there is some internal intellisense.
Otheriwse it is easy to do a check in the tail-javascript if request.isAjax() and leave out the domready wrapper. ** Martin 2010/5/19 Jeremy Thomerson <jer...@wickettraining.com>: > DOM ready will only be fired when the dom is ready - which is as the page is > loading / rendering. When you do an AJAX replace, the DOM is not completely > reinitialized - only part of it is replaced. You would not want a dom ready > event to fire again because it would reinitialize everything in the dom that > was listening to that event. Thus, you must fire the reinitialization > yourself on modified components. > > -- > Jeremy Thomerson > http://www.wickettraining.com > > > > On Tue, May 18, 2010 at 4:35 PM, Ivoneta <ietaraz...@gmail.com> wrote: > >> >> I work with JQuery. >> I read in another post that the dom ready event isn't fired. >> it is right? >> >> I suspect I should do the js initializes every time! >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/replace-panel-problems-tp2221878p2221952.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
