Skip to content

Conversation

@onlyurei
Copy link

The old Chrome bug has been reported to be fixed.
http://code.google.com/p/chromium/issues/detail?id=63040
Initial testings in my app using this lib show that the route handlers aren't called twice on initial page load and after hard refreshes after this change.

The old Chrome bug has been reported to be fixed.
http://code.google.com/p/chromium/issues/detail?id=63040
Initial testings in my app using this lib shows the route handlers aren't called twice on initial page load and after hard refreshes.
@mbektimirov
Copy link

So what about this PR? Are you planning to do any movement on this? With this 500 ms fix I get object is not a function for onpopstate because setTimeout callback does not have time to execute when I need it.

@mehcode
Copy link

mehcode commented Mar 31, 2015

Is there anything I can do to help this get merged -- this is blocking us

@cmwelsh
Copy link

cmwelsh commented Apr 1, 2015

This is a duplicate of my pull request #279.

@mehcode Just fork the project. This project is barely maintained.

@cmwelsh
Copy link

cmwelsh commented Apr 1, 2015

Also note that this fix causes bug #227 to happen pretty consistently on iOS devices. For that and other reasons I'm switching my project to react-router.

@mehcode
Copy link

mehcode commented Apr 2, 2015

@cmwelsh Yep, noticed that yesterday. We switched to react-router yesterday. It's still a new project so it was pretty easy.

SpaceK33z added a commit to CodeYellowBV/tarantino that referenced this pull request Dec 1, 2016
@SpaceK33z
Copy link

SpaceK33z commented Dec 1, 2016

For anyone bumping into this, I've fixed this in my fork, published it on npm and plan to maintain it (with that I mean, I will review PR's and fix critical issues).

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.

5 participants