Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out getHash vs getFragment solution #8

Open
geekdave opened this issue Jul 18, 2012 · 1 comment
Open

Figure out getHash vs getFragment solution #8

geekdave opened this issue Jul 18, 2012 · 1 comment

Comments

@geekdave
Copy link
Contributor

We use this code to trigger a new subroute immediate upon initialization:

        // grab the full URL
        var hash = Backbone.history.getHash();

        // Trigger the subroute immediately.  this supports the case where 
        // a user directly navigates to a URL with a subroute on the first page load.
        Backbone.history.loadUrl( hash );

For some, only getHash() works. For others, only getFragment() works.

I haven't had the time to track down why, since some of these cases involve using push state, which I am not using in any projects. If anyone can help out with getting to the bottom of this, it would be a big help.

Some discussion on the issue, and a previous pull request, can be found here.

Thanks to @jtuulos and @MMRandy for your feedback so far.

@amakhrov
Copy link
Contributor

Does the issue still exist?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants