This will not be applied before wicket.next. Until then, I think we should 
really reconsider the current domready implementation on IE. Perhaps, we can 
'borrow' JQuery's ready implementation for now?

On Friday 30 September 2011 09:18:32 Martin Makundi wrote:
> Umh.. not 1.4.17? We are in 1.4.17.
> 
> 2011/9/30 Martin Makundi <[email protected]>:
> > This affects 1.4 also?
> > 
> > 2011/9/30 Martin Grigorov <[email protected]>:
> >> Hopefully with https://github.com/martin-g/wicket/tree/ajax-jquery
> >> merged in Wicket.next this kind of problems will be much less
> >> 
> >> This branch is work in progress.
> >> 
> >> On Fri, Sep 30, 2011 at 8:56 AM, Emond Papegaaij
> >> 
> >> <[email protected]> wrote:
> >>> Even though we came up with the fix ourselves, it did not solve the
> >>> problem for us in all cases. The fix for 4080 fixed one of our apps,
> >>> but the other still is very broken. Someone with knowledge about
> >>> domready in IE should really look at this. We've abandoned wicket's
> >>> domready and now use WiQuery to pass all domready events to JQuery's
> >>> $(document).ready(), which works fine.
> >>> 
> >>> Best regards,
> >>> Emond
> >>> 
> >>> On Friday 30 September 2011 08:49:46 Martin Grigorov wrote:
> >>>> 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

Reply via email to