Re: AW: Header requiring to be contributed through page load and not ajax...
Stefan Lindner wrote: 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 example of a browser crash: uncaught exception: [Exception... "Component returned failure code: 0x804b0049 (NS_ERROR_ALREADY_OPENED) [nsIXMLHttpRequest.send]" nsresult: "0x804b0049 (NS_ERROR_ALREADY_OPENED)" location: "JS frame :: http://localhost:8080/resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax.js :: anonymous :: line 841" data: no] - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: AW: Header requiring to be contributed through page load and not ajax...
Stefan Lindner wrote: 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 thanks for this answer Stefan Let's go for an exemple: there is no jquery related header, and then an ajax request contributes the required header lib (in the proper order, or at least so is it when loading "normally"). Then any jquery code executed afterwards fail, for example with "$ is not defined" and sometimes, with some plugins, in a worse way (like browser crash). In these cases the debugger wasn't working at all, in the previous it was fairly obvious that some jquery init hadn't been done. when the jquery and plugins files are present on page load, none of these issues appear. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
AW: Header requiring to be contributed through page load and not ajax...
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 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
