If you note the code below, basically I want the page with id "testpage" to not appear in history. This appears to be the case, but when I close this page I transition back two pages in history, back to Page 1. I appear to have this wrong or do not understand what the point of this option is. Note that my code below is a multipage document, this is just for simplicity here, but I am using single page templates and the outcome is the same. I want to close Page 3 and go back to Page 2, but I guess as the URL has not changed data-rel="back" takes me back to Page 1. Could be me but this just seems like the wrong action?
Can anyone spot the obvious mistake I'm making? Thanks.
I have a page where the user can edit some data. I want that page to not be added to the history stack. This is the case and works with the code above. Once entered I programmatically change pages, no problem there.
However if the user changes their mind and wants to back out of the edit page, then data-rel=back takes me "back" two pages because the edit page has not updated the history stack. I can of course use a Cancel button and take control of that, but if the back button on the browser is used I have a problem.
It doesn't seem (to me) that that should be the intended behaviour.
Leave a comment on AnthonyC's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic