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.
Currently, it appears that by default in JQM 1.0a4.1, elements such as anchors, forms, etc. that allow page navigation always update the hash and page history navigation unless one explictly captures the click or submit event and then invokes the $.mobile.changePage method themselves specifying that the hash not be updated. It would be quite helpful if a data attribute could be supported that would allow the developer to specify whether they want the hash to be changed for an anchor or form. As an example:
Currently, it appears that by default in JQM 1.0a4.1, elements such as anchors, forms, etc. that allow page navigation always update the hash and page history navigation unless one explictly captures the click or submit event and then invokes the $.mobile.changePage method themselves specifying that the hash not be updated. It would be quite helpful if a data attribute could be supported that would allow the developer to specify whether they want the hash to be changed for an anchor or form. As an example:
The text was updated successfully, but these errors were encountered: