Forums

I'm in the process of building a web page using Y.App and 3.6.0pr2. I'm modeling after the GitHub Contributors example. For my app, I'm setting the root to be something like this:



I then have a path set up as follows:



If I define handleId as follows:



With serverRouting = undefined and viewing Firefox, using the URL http://localhost/my/custom/route/1 will alert "1". However, when I view the URL http://localhost/my/custom/route#/1/ in IE or with serverRouting = false (so no HTML5 functionality is used), the alert will be "my". It's as if the params logic isn't using the root attribute when it's not HTML 5. Am I doing something wrong?

I think the issue has to do with the use of the ending "/". Locally, I've set it up so both of the following paths will return your sample page:

http://localhost/customroot/AppTest
http://localhost/customroot/AppTest/

and set root as:



I'm using ASP.NET MVC, and both of those routes will match to the same action. If I visit this URL:

http://localhost/customroot/AppTest/#/1/

it will correctly output "1".

If I visit this URL:

http://localhost/customroot/AppTest#/1/ (notice a / is missing)

it will output "customroot".

So clearly, the trailing "/" is causing a difference. This is fine, but I would prefer that the latter URL work. So, to fix this, I adjusted the root to be:

(removed the final /)

However, this does not fix the problem, as after doing so, the output for the second URL is still "customroot". I also attempted to change the route path from '/:id/*' to ':id/*' and that just outputs blank.

Ticket created: http://yuilibrary.com/projects/yui3/ticket/2532486

If anyone else runs into this issue, I was able to workaround it by having my server logic redirect to the URL and append the ending "/" if it was missing. I then used a root that ended in a "/".

Okay here's the pattern I'm going to use for hash-based paths and "spreading" over the `location`'s `pathname` and `hash` parts:

Example Router Setups

Click here to see the revision history on this Gist.

Notice in the last three examples the `root` is part of the hash, this is because the `root` does not equal the current URL's `pathname` (the full path) or the URL's path-root (the `pathname` ending at the last slash).

The reason the URL's path-root is also checked is to deal with a common case where the URL's `pathname` is "/app/index.html" and the router's `root` is "/app/".

Here's the diff of the changes I'm going to make which will solve this issue:

Router Diff

Click here to see the revision history on this Gist.