We are having safari 3.1.2 issues with wicket's 1.4 domready in wicket-event used in wicket-ajax blocking our custom mootools code that is loading on domready as well. Anybody have any ideas on how to better load custom js on domready without conflicting with wicket's? It seems that domready is being called to soon before our scripts have a chance to load.. Basically all of our custom javascript is not loading when the wicket-ajax file is being included.
Also, is there an easy way to put javascript in the bottom of your page before the ending body tag? Sortof like <wicket:head></wicket:head>, or <wicket:foot></wicket:foot>. Please help! -- View this message in context: http://www.nabble.com/Wicket-Ajax-Safari-DomReady-Conflicts-tp18841457p18841457.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
