I have an application which relies on can.route to capture the #change when the user clicks on a link. href for the link is having pattern '#!'. Once the change is capture by the can route utility, i am seeing the hash in the browser changing to #!&.
This is causing an additional entry in browser history stack. Has anyone faced a similar issue?
Appreciate your help.