Using stop() still changes the URL to the next path

When firing stop() inside of the global triggers.exit, the expected behavior is that the user is not taken to the next route. From what I can see, FlowRouter still updates all its internals to reflect that we’re on the new route, even though the page doesn’t actually change.

FlowRouter.triggers.exit([pageChange])

pageChange = function(context,redirect,stop) {                                                                        
   if (context.path.indexOf('step=') > -1                                                                         
        && !confirm('Are you sure you want to leave this page?'                                                       
            + ' You haven\'t finished yet.')                                                          
    ) {
        stop()
    }
}

This guy seems to have had a similar problem and solved it, but the pull request was never merged? https://github.com/kadirahq/flow-router/pull/681

[jasongrishkoff]

To me, “stop” would imply that I want to cancel my routing and stay where I am. The fact that it only fires after the URI has changed seems wrong. I’ve already used a workaround, so in a sense this is solved.

[dr-dimitru]

@jasongrishkoff thank you.

We did additional checking, there is no easy way (or at least we haven’t found any) to change this behavior, this part remained unchanged from original flow router.