-
Notifications
You must be signed in to change notification settings - Fork 503
actions on IOS6 #265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Instead of adding a phantom timestamp, try adding the following line in your document.ready function or before your $('#tableContainer').jtable() call.
|
I tried that first. Along with a dozen other things. Try a simple web page that return a timestamp. Call it consecutively from your desktop then from an IOS6 phone / device. My test used ajax calls with IIS7 cache disabled, meta tags disabling cache, and ajax cache disabled (as you suggest). Another source…. From: LamboJay [mailto:notifications@github.com] Instead of adding a phantom timestamp, try adding the following line in your document.ready function or before your $('#tableContainer').jtable() call. $.ajaxSetup({ cache: false }); — |
Interesting read, Thanks for the link. |
It's very interesting. In next versions, I'll add a feature to jTable that allows to dynamically create action URLs. Thus, you will be able to add timestamp easily. That's what I can say for now. |
Sounds good. From: hikalkan [mailto:notifications@github.com] It's very interesting. In next versions, I'll add a feature to jTable that allows to dynamically create action URLs. Thus, you will be able to add timestamp easily. That's what I can say for now. — |
Just leaving a note about an issue I am dealing with. It appears there is a bug in IOS6 where it caches absolutely everything. This is forcing me to rewrite a lot of code adding a timestamp as a phantom parameter to every call. I had to made a change to the ajax call in this code base as well. See change for delete call below.....
The text was updated successfully, but these errors were encountered: