documentcloud/backbone — pull request #1497 by claymation (2012-07-19 00:51:31+00:00)
Title: Remove a conditional that prevents (re)navigating to the current fragment

I'm writing an application that has a logged-in and logged-out state. If a logged-out user accesses the application using a link that contains a hash fragment (http://host/app#fragment), an authentication form is displayed and I do not populate any of the application's model collections. Once the user authenticates, I would like to be able to trigger the navigation event again, with `router.navigate(document.location.hash)`. But the router currently prevents navigating to the current location. Is this an optimization, or is there a reason to prevent such behavior?