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

fix: back button doesn't work when URL contains hash #16

Merged
2 commits merged into from
Mar 13, 2015

Conversation

vevo-arthur-klepchukov
Copy link
Contributor

Replacing our no-longer-maintained history polyfill with native HTML5
History pushState and popState.

browserstate/history.js#390
browserstate/history.js#276

Replacing our no-longer-maintained history polyfill with native HTML5
History pushState and popState.

browserstate/history.js#390
browserstate/history.js#276
@vevo-arthur-klepchukov
Copy link
Contributor Author

Builds failing seem unrelated. @demetriusj please review.

@@ -189,16 +189,25 @@ if(process.env.SERVER_ENV) {
}
});

var currentLocation = location.pathname + location.search;
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hey dude can you please inline this function and use a closure to not expose the currentLocation globally. additionally we will need to test if its a good idea to ignore the first pop state

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's test ignoring the first pop state and revise if needed.

ghost pushed a commit that referenced this pull request Mar 13, 2015
fix: back button doesn't work when URL contains hash
@ghost ghost merged commit 35e0fe8 into master Mar 13, 2015
@ghost ghost deleted the fix-back-button-with-hashes branch March 13, 2015 20:06
This pull request was closed.
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

Successfully merging this pull request may close these issues.

2 participants