[jira] [Commented] (WICKET-4166) Wicket.Event.add(windows, "domready", ...) is triggered too soon in IE7 with wicket 1.5.x

["Alex Grant (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256175#comment-13256175 ] 

Alex Grant commented on WICKET-4166:
------------------------------------

In case anybody else runs across this issue:

I had this issue with Wicket 1.5.5. 
ondomready would fire before the other components were loaded in IE7 & IE8 so document.getElementById('someId') would return null. 

It turned out to be a problem with jQuery - upgrading from 1.7 to 1.7.2 fixed the problem. Just importing jQuery was enough to cause the problem; you didn't need to actually use it.
                
> Wicket.Event.add(windows, "domready", ...) is triggered too soon in IE7 with wicket 1.5.x
> -----------------------------------------------------------------------------------------
>
>                 Key: WICKET-4166
>                 URL: https://issues.apache.org/jira/browse/WICKET-4166
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.1, 1.5.2
>         Environment: IE7
> windows XP
> Wicket 1.5.x
>            Reporter: Gabriel LANDON
>              Labels: ie7, javascript
>         Attachments: js0.JPG, js1.JPG, js2.JPG
>
>
> When using wicektstuff-gmap2-example with IE7, the code Wicket.Event.add(window, "domready", function(event) { new WicketMap2('map1');  is triggered before the page is ready. 
> So an error is raised saying that "WicketMap2 is undefined".
> It's working fine with IE8/IE9, FF7, Chrome and Opera.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira