initial handler fired twice

[sulram]

Hello there!

I've created an strategy to always redirect users to home, and them open the desired uri via ajax and director.

When users try entering example.com/page1, they are redirected to example.com/#/page1.

I'm using pushState and director automatically corrects the route, removing the hash. That's cool!

The problem: sometimes director fires the route callback twice.

Why is that?

[beaugunderson]

Glad to try and debug this if you can provide a small test that shows the incorrect behavior! :)

[sulram]

hi @beaugunderson
I notice that there was a little info in init method

        // There is an old bug in Chrome that causes onpopstate to fire even
        // upon initial page load. Since the handler is run manually in init(),
        // this would cause Chrome to run it twise. Currently the only
        // workaround seems to be to set the handler after the initial page load
        // http://code.google.com/p/chromium/issues/detail?id=63040

I solved the bug in SAFARI and SAFARI IOS by calling init after window.onload
What do you think about this?
thanks!

[cmwelsh]

I think the only robust solution is to refuse firing the same route twice in a row. The router instance should track the current route.