It seems there is an update for IE that broke the state ... See also https://issues.apache.org/jira/browse/WICKET-4080
On Fri, Sep 30, 2011 at 8:27 AM, Martin Makundi <[email protected]> wrote: > Hi! > > I have noticed lots of document.body=null situations with domready in > IE, I am currently trying out the following fix to wicket-event.js: > > var domReady = function() { > function onBodyLoadedSafely() { > if (document.body) { > if (window.loaded) > return; > window.loaded = true; > > // invoke the handlers > > Wicket.Event.fireDomReadyHandlers(); > } else { > > window.setTimeout(onBodyLoadedSafely, 100); > } > } > > onBodyLoadedSafely(); > }.bind(this); > > > Domready is postponed until document.body > > > ** > Martin > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
