Router hijacks the whole host:port

[rupesh97]

We are using router with useFragments in a single page app. We route based on fragment values, e.g.
http://foo.com/some/path.html#hash1. This app also has links to other urls on the same website (they always specify target="_blank").

Unfortunately, Router hijacks all urls on that host:port, so those links don't work unless the user presses Ctrl or Shift. They just get sent to http://foo.com/some/path.html# (empty fragment).

Can we fix this? At least in the useFragment case, there is no reason to meddle with any other path, right?

[justinfagnani]

You're probably using the Angular fork of the router, but we'll fix this were too. I think the solution is to specify a root URL, and paths outside of it won't be handled by the router.