[ 
https://issues.apache.org/jira/browse/TAP5-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ulrich Stärk updated TAP5-1193:
-------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated more than 1.5 years ago, has no assignee, 
affects an old version of Tapestry that is not actively developed anymore, and 
is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of 
Tapestry, please update it as soon as possible. In the case of a feature 
request, please discuss it with the Tapestry developer community on the 
d...@tapestry.apache.org mailing list first.
                
> tapestry.js prevents using the back/forward browser cache
> ---------------------------------------------------------
>
>                 Key: TAP5-1193
>                 URL: https://issues.apache.org/jira/browse/TAP5-1193
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.4
>            Reporter: Dan Adams
>              Labels: bulk-close-candidate
>
> At the bottom of tapestry.js is the following:
> // Ajax code needs to know to do nothing after the window is unloaded.
> Event.observe(window, "beforeunload", function()
> {
>     Tapestry.windowUnloaded = true;
> });
> Assume you have a page that does this:
>  - loads in some initial state
>  - user does something causing a ajax request that changes the DOM
>  - user clicks a link to go to another page
>  - user clicks back button
> rather than getting the state of the page before they left the user will get 
> the original state of the page including the DOM and js state and the load 
> handlers will be run. Using the hash method of maintaining ajax history (or 
> maybe a cookie) is really not an option in this case because the DOM is out 
> of date. You'd need to do an extra ajax request to the server to restore the 
> state and the user experience would be really poor.
> There needs to be at least of the option of disabling this for pages that 
> need this behavior.
> See 
> http://stackoverflow.com/questions/158319/cross-browser-onload-event-and-the-back-button

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to