I use onDomReady functionality at many places in my jWicket jQuery-integration. I don't know of any general problem (no guarantee that there isn't one) with jQuery and Wickets onDomReady. Of course you have to ensure that the library (and perhaps additional files) is loaded in correct order with other libraries of jQuery. Did you use a debugger (e.g. firebug) to examine your javascript behavior?
Stefan -----Ursprüngliche Nachricht----- Von: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Gesendet: Donnerstag, 9. September 2010 22:42 An: users@wicket.apache.org Betreff: Re: Header requiring to be contributed through page load and not ajax... dunno then, you may want to talk to jquery people and see what they recommend. we cant really fire the onload event again because some scripts may have already been executed...like i said, see what jquery folks say. -igor On Thu, Sep 9, 2010 at 1:38 PM, Joseph Pachod <josephpac...@thomas-daily.de> wrote: > instead of $(document).ready(function() use wicket's > iheadercontributor's response.writeondomreadyjavascriptthanks for the > answer > > I do so for my own stuff, but jquery plugin don't. > > similarly, the core jquery file import won't work when added through ajax. > > --------------------------------------------------------------------- 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
