You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Michal Wegrzyn (JIRA)" <ji...@apache.org> on 2012/06/21 14:04:43 UTC
[jira] [Commented] (WICKET-4166) Wicket.Event.add(windows,
"domready", ...) is triggered too soon in IE7 with wicket 1.5.x
[ https://issues.apache.org/jira/browse/WICKET-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398369#comment-13398369 ]
Michal Wegrzyn commented on WICKET-4166:
----------------------------------------
thanks Alex, helped.
I had exactly the same issue with FileUpload's progressbar - org.apache.wicket.extensions.ajax.markup.html.form.upload.UploadProgressBar/progressbar.js:
bind : function(formid) {
formElement = Wicket.$(formid);
this.originalCallback = formElement.onsubmit;
formElement.onsubmit = this.submitCallback.bind(this);
},
formElement was null.
Works fine with jQuery 1.7.2.
> 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