You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 8, 2021. It is now read-only.
I am trying to refresh a page by reloading it from the server. From what I have been able find in the documentation, the following code should do the trick:
The first problem is that it does not appear to do anything unless I add "reloadPage: true" into the options even though the documentation says "reloadPage" is deprecated and "reload" should be used instead.
But the real problem is that the reload corrupts my checkbox on the page by replicating its label. I seems that the problem is caused by two copies of the page residing in the DOM simultaneously at least for some period of time and the checkbox ID appears twice during that time.
I suppose we should document for the reload option that, if your page is to be reload-able you should design it in such a way that the temporary presence of duplicate IDs does not interfere with the process.
I will keep this open for the misbehaving pagecontainer reload option.
I am trying to refresh a page by reloading it from the server. From what I have been able find in the documentation, the following code should do the trick:
jQuery.mobile.pageContainer.pagecontainer('change', window.location.href, { reload: true });
The first problem is that it does not appear to do anything unless I add "reloadPage: true" into the options even though the documentation says "reloadPage" is deprecated and "reload" should be used instead.
But the real problem is that the reload corrupts my checkbox on the page by replicating its label. I seems that the problem is caused by two copies of the page residing in the DOM simultaneously at least for some period of time and the checkbox ID appears twice during that time.
The test case can be found on at http://jsbin.com/huvoraba/165
The text was updated successfully, but these errors were encountered: