[
https://issues.apache.org/jira/browse/WICKET-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298409#comment-14298409
]
Sven Meier commented on WICKET-5822:
------------------------------------
What's the reason you didn't use "unload" instead? Do you see a memory leak
problem with that?
JavaScript event handlers have the ability to stop unloading from
"beforeunload". It wouldn't be nice to lose all timers on the page, just
because a confirmation popup returns false.
I just tried "unload" instead on Firefox, this seems to work fine.
> AjaxSelfUpdatingTimer stops working after ajax download
> -------------------------------------------------------
>
> Key: WICKET-5822
> URL: https://issues.apache.org/jira/browse/WICKET-5822
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.18.0
> Environment: Linux
> Reporter: Elvis Ciocoiu
> Assignee: Sven Meier
> Attachments: timer test.zip
>
>
> I've encountered a strange behavior related to AjaxSelfUpdatingTimerBahavior.
> It triggers normally until I click a link that downloads a dynamic resource.
> The ajax download link is constructed using the recommendations from:
> https://cwiki.apache.org/confluence/display/WICKET/AJAX+update+and+file+download+in+one+blow
> The problem seems to be related to:
> target.appendJavaScript("setTimeout(\"window.location.href='"
> + url + "'\", 100);");
> from ajax download initiate, but if i comment it the download doesn't work
> anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
