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 using backbone and have attempted to turn off all JQM processing
$(document).bind("mobileinit", function () {
$.mobile.ajaxEnabled = false;
$.mobile.linkBindingEnabled = false;
$.mobile.hashListeningEnabled = false;
$.mobile.pushStateEnabled = false;
$.mobile.changePage.defaults.changeHash = false;
);
I handle the changing of the page with the $.mobile.changePage() method
As resolved in that issue #5483, this works with simple hash like /#groups or /#settings, but when I have hash that includes parameters, like http://localhost:8080/#taskGroupDetails/7
I am seeing attempts by JQM to process the url.
In particular, I am seeing a 404 when JQM attempts to call backend with http://localhost:8080/taskGroupDetails/7 (notice lack of hash)
I am seeing this 404 before my backbone router code get executed. There should not be an attempt by JQM to perform this request.
This is issue similar to #5483
I am using backbone and have attempted to turn off all JQM processing
$(document).bind("mobileinit", function () {
$.mobile.ajaxEnabled = false;
$.mobile.linkBindingEnabled = false;
$.mobile.hashListeningEnabled = false;
$.mobile.pushStateEnabled = false;
$.mobile.changePage.defaults.changeHash = false;
);
I handle the changing of the page with the $.mobile.changePage() method
$.mobile.changePage($(view.el), {
changeHash:false,
});
As resolved in that issue #5483, this works with simple hash like /#groups or /#settings, but when I have hash that includes parameters, like http://localhost:8080/#taskGroupDetails/7
I am seeing attempts by JQM to process the url.
In particular, I am seeing a 404 when JQM attempts to call backend with
http://localhost:8080/taskGroupDetails/7 (notice lack of hash)
I am seeing this 404 before my backbone router code get executed. There should not be an attempt by JQM to perform this request.
Another side effect is that all subsequent URL processing now includes 'taskGroupDetails' in the URL, e.g., http://localhost:8080/taskGroupDetails/7/...now-we-see-the-correct-piece-of-url...
I can provide sample code as necessary.
The text was updated successfully, but these errors were encountered: