I figured as much just thought I'd check on the foot thing, we can always add a panel that you override as needed in the base page if necessary. Safari/Webkit is notorious for firing the mechanisms used in checking for domready later than other browsers. Just look at the code in wicket-event.js for it's safari domready implementation and you'll see it is doing what everybody has to do with safari, run a timer and keep checking until Safari decides to fire it. Which is why putting it at the bottom of the document can help sometimes because it might delay the loading of the script somewhat and hope for a little better timing.
Normally you can rely on this type of domready detection in Safari without a hitch but in this specific case Wicket's domready was somehow making the browser fire the event or blocking our timer-based safari domready (mootools) from detecting the event. It was sporadic of course because Safari seems to randomize when it chooses to load scripts and fire events. BTW, this is all in the name of a faster page load, hence their marketing phrases. In the end we think we solved it by putting our function calls for safari in onload instead of domready. Probably because the onload event is not conflicting with the wicket domready anymore. igor.vaynberg wrote: > > yeah, i know what it is and what its for. i wouldnt call it a rule, > more of an observation... > > so what exactly was the point of doing all the work for those > domready/onload events? is it not more correct form to use those? > > -igor > > On Tue, Aug 5, 2008 at 4:22 PM, Martijn Dashorst > <[EMAIL PROTECTED]> wrote: >> loading scripts at the end of the document just prior to the </body> >> tag makes rendering the page more efficient. It is one of the golden >> rules for page performance (see the yslow plugin for firefox). >> >> Martijn >> >> On Wed, Aug 6, 2008 at 1:00 AM, Igor Vaynberg <[EMAIL PROTECTED]> >> wrote: >>> is this happening only in safari? >>> >>> no, there is no wicket:foot because there is no <foot> html >>> element...and what is the point of putting everything right before >>> </body> since we now have nice event handling such as domready/window >>> onload... >>> >>> -igor >>> >>> On Tue, Aug 5, 2008 at 3:53 PM, zonathen <[EMAIL PROTECTED]> wrote: >>>> >>>> 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] >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> >> >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> Apache Wicket 1.3.4 is released >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. >> >> --------------------------------------------------------------------- >> 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] > > > -- View this message in context: http://www.nabble.com/Wicket-Ajax-Safari-DomReady-Conflicts-tp18841457p18862359.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]
