I have a main page, lets name it ABC.htm. On it I have a link to a second page named FOO.htm. Both of these pages are built with JQM. How do I make certain that the DOM from ABC.htm is not cached after the user clicks on the link and transitions to FOO.htm?
I know that rel=external will do it but it has the unwanted side effect of opening a browser window (when running chromeless).
I have tried setting data-dom-cache but it should be false by defalut.
I realize that I didn't give a lot of background. I am trying to distill down what I think the problem is.
I have a popup dialog that should be opened when a button is pressed. It works properly on desktop browsers and on Droid. On iPhone and iPad (Safari) I discovered that it wasn't opening. If the page containing the button is refreshed it will work. I took it to Safari and Chrome on the desktop and changed the useragent to iPhone. It works properly on Safari. With Chrome it is the same behavior as the iPhone/iPad. Will not work unless the page is refreshed.
I have taken the page source after initial load (when it is not working) and after refresh (when it is working) and used WinDiff to compare the two. They are identical.
Here is the markup for the button that should open the dialog:
My markup and page structure are correct. JQM pages structure properly. Since this is a dialog it is a multi-page. I have used tools to ensure that all elements are properly closed. For full disclosure below is the page source for the entire page.
Please excuse my ignorance on this but I am tired of fighting this. I need to do a file upload on one of my JQuery Mobile pages. I'm doing this in .NET MVC 3, just for the record.
I have four pages, A, B, C, and D. A, B, and D gather info and/or save stuff. Page C does the upload.
I know that I need to disable ajaxForms in order to accomplish the upload. So below is how I have my javascript stuff setup in the <head> for each page.
If I navigate normally into the site through pages A, then B, and then C it caches the <head> declarations from A and carries them to C. So the my-noajax.js doesn't happen.
If I enter the site directly to page C all is good.