[
https://issues.apache.org/jira/browse/TAP5-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969893#action_12969893
]
Raul Montes commented on TAP5-957:
----------------------------------
Exactly that's the main problem with setting windowUnloaded=true on
beforeunload event. It is triggered with download links... what I did as a
workaround is to put a target="_blank" on links to download files. That way the
beforeUnload event is not triggered. But I still think the correct event to
listen is unload event, not beforeunload event. Someone on the Tapestry team
can explain why use beforeunload instead? Is there a problem replacing it with
unload event?
> Unexcept "beforeunload" event generated by ie
> ---------------------------------------------
>
> Key: TAP5-957
> URL: https://issues.apache.org/jira/browse/TAP5-957
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: mindhawk
> Priority: Minor
>
> IE will generate a "beforeunload " event when a link such as "<a
> href='javascript:show()'>show</a>" is clicked. So Tapestry.windowUnloaded is
> set to true. That means all ajax request have no chance to refresh the page
> after this event.
> Now, I have to set Tapestry.windowUnloaded=false, every time I want to send a
> ajax request. I don't think thisis a good practice.
> I think there will be some more smart approach to replace
> Tapestry.windowUnloaded, or just remove it. because, the request is sent to
> the server no matter the value is true or false. This value is only discard
> the responses from the server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
