jQuery Forum

the only way to make this work properly is by using the global:

$.mobile.ajaxEnabled = false;

Actually, that's not entirely true.  You can remove previous pages after transition.  Something I almost always start with in new jqm projects.

$(document).on('pageshow', function (event, ui) {
    // Remove the previous page
    $(ui.prevPage).remove();
});

Do you mean cache as in HTTP static content caching?

If so, you have to set expires headers on your requests at the code or web server level.

Right.

That's why the remove code above should have worked.

Where do you add it?  External file, inline somewhere?  You should be able to use inspector or firebug to verify that there's only 1 page after transitions.

That would circumvent the whole point of keeping the page in the DOM. The code posted by tate would belong in the global js file, not within each page that needs it. You don't want it re-executing that binding code on every request.

-- Kevin

Maybe I am missing something but isn't data-dom-cache="true" setting used so the page will refresh the cache? 

Maybe I am missing something but isn't data-dom-cache="true" setting used so the page will refresh the cache?

It's the opposite.

data-dom-cache-"true" prevents the page from being removed from the DOM.

I use this quite frequently, in conjunction with iScroll, If there are a small number of short lists in an application that the user will re-visit often, I cache them. It's particularly useful when the user might select an item in the list, click on it to visit the corresponding page, then go back, and may perhaps want to visit the next or previous item in the list. When using iScroll, when they go back, the scroll position is unchanged. So, they do not lose their place.

(Yes, I know JQM starting with 1.1 does this too, but it's nicer with iScroll, because you can retrofit the old 1.0 transitions, as well, while still retaining scroll position.)

There is no corresponding data- attribute that would force it to be removed early. It will normally be removed when you navigate to a third page. The page is normally retained in the DOM for the benefit of "back". "back" will normally take you back to the previous page without refreshing it from the server.

This certainly seems to be an oversight in the design. There is an option to force reload if you use $.mobile.changePage(), but no way provided to do this from a link.

Hey,

What I posted will work in your situation.  The reason why data-dom-cache="false" is insufficient is because the first page you visit is ALWAYS kept in the DOM.

And like Kevin said, make sure you put that code in a global js file in the head AFTER jquery and jquery mobile.  Also, it might only work for 1.2 since the page events changed so much from 1.1 to 1.2.

Set a breakpoint in the inspector on that line and make sure it's running after each page transition.  On the first page, previous page would obviously be null and hence not do anything.

Steven