I believe that's a known bug that should be fixed in 1.2.7. It's definitely fixed in 1.3.
-Matej On 9/25/07, John Carlson <[EMAIL PROTECTED]> wrote: > Eelco, > > I'm using 1.2.5 > > John > > On 9/24/07, John Carlson <[EMAIL PROTECTED]> wrote: > > I have had several pages that will not initially load the wicket-ajax > > functionality. The page will load but the throttler is missing or it > > will complain that submitFormById is undefined. Refreshing the page > > loads the ajax scripts and everything works fine. I did alittle > > snooping and found that on the first load wicket doesn't add the > > wicket-ajax.js to the markup. That's why some functions are > undefined. > > I setoutputmarkupid(true) on all the related things as far I can tell. > > Does the order of setting markup Id and adding things to the page > > matter? ie. > > No, it shouldn't. What version of Wicket are you using? The first > component or behavior that does a header contribution of > wicket-ajax.js (any AjaxBehavior that is shipped with the wicket core > projects) should cause the script to be loaded. > > Whether you call setOutputMarkupId is unrelated to whether scripts are > loaded. > > Eelco > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
