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

[1.3.0-beta.1] Hash Processing error when hash has parameters (e.g., /#taskGroupDetails/7) #5567

Closed
bjwiederholt opened this Issue Feb 1, 2013 · 4 comments

Comments

Projects
None yet
5 participants
@bjwiederholt

bjwiederholt commented Feb 1, 2013

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.

@pYr0x

This comment has been minimized.

Show comment
Hide comment
@pYr0x

pYr0x Feb 2, 2013

same problem.. same issue

pYr0x commented Feb 2, 2013

same problem.. same issue

@d-as

This comment has been minimized.

Show comment
Hide comment
@d-as

d-as Mar 10, 2013

Same here.

d-as commented Mar 10, 2013

Same here.

@jaspermdegroot jaspermdegroot modified the milestone: 1.5.0 Jun 5, 2014

@arschmitz

This comment has been minimized.

Show comment
Hide comment
@arschmitz

arschmitz Jun 19, 2015

Member

looks like this was fixed already from the links closing

Member

arschmitz commented Jun 19, 2015

looks like this was fixed already from the links closing

@arschmitz arschmitz closed this Jun 19, 2015

@pYr0x

This comment has been minimized.

Show comment
Hide comment
@pYr0x

pYr0x Jun 20, 2015

i didnt see a fix?

pYr0x commented Jun 20, 2015

i didnt see a fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment