URL/URI and path styles for navigation

URL/URI and path styles for navigation

A few months ago I was pretty excited to run into jQuery mobile. I needed to write a mobile app and being a pretty big fan of jQuery I figured it would be a great fit.

I immediately started running into issues with the way that jQuery mobile was handling URLs for its fancy AJAX navigation. I found some temporary workarounds (mainly by way of disabling AJAX entirely for all form submission and about 50% of the links) in the hopes that it would be fixed sooner rather than later.


The problem

Almost all web frameworks I know of use some sort of base URL management and generate URLs from the root of the app. In most cases that is the domain name in a production environment. ( the URL for   http://example.com/category/5/item/3 would be generated as /category/5/item/3 )

I want someone to be able to get a link to http://example.com/category/5 and have things start in that valid state. On that page, I generate a link to item 3 that looks like /category/5/item/3 . In 0.3a this sorta worked... it would rewrite the link to /category/5#/category/5/item/3

In 0.4a pre, for some reason it is actually making a request to /item/3 by way of AJAX so I'm getting an error. Why is it now requesting /item/3 behind the scenes instead of /category/5/item/3?

I'm not really sure why this is happening but it makes me feel like things are sliding backward on better support of this style of URL/URI management.


The question

This style of URL generation is pretty standard in any dynamic language I've worked in so I have a hard time believing that this isn't already on the radar. Is this a known issue that has a priority of some sort? Is there an issue on GitHub or a post somewhere that someone link to it so I can follow it?

I believe all of the docs and demos are pretty basic HTML with child pages only linking to other child pages ( /docs/buttons/ => /docs/buttons/#buttons-grouped.html )... there are no paths back to the parents or siblings. As such it is probably pretty hard to see that there is even a bug just by browsing the docs.

I'd be happy to help build some test pages to illustrate the problem so that it can be tested regularly. Is that something that could be useful? Suggestions on how to go about this would be greatly appreciated. I'm anxious to make sure that this is testable and can get addressed quickly.