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

Switch to use the native history API #9

Open
stof opened this issue Sep 10, 2011 · 2 comments
Open

Switch to use the native history API #9

stof opened this issue Sep 10, 2011 · 2 comments

Comments

@stof
Copy link
Contributor

stof commented Sep 10, 2011

I often have issue when using http://slides.seld.be/ with the jquery.history.js file that get aborted after 20s or so, and so breaking slippy. As modern browsers now support the history API, it could be better to use it instead (and so no issue about loading a file for them) and fallback to a polyfill for old browsers (IE...). What do you think about it ?

@Seldaek
Copy link
Owner

Seldaek commented Sep 13, 2011

I guess relying on the history API would be ok, as long as it can fallback on the current solution. I'm not a fan of excluding older browsers.

I'm not sure I get your problem though, jquery.history.js works just fine here.

@stof
Copy link
Contributor Author

stof commented Sep 13, 2011

Well, for me, the request is aborted after about 20s for half of the request I do (and when it fails, it is generally failing for a while thus making it unusable). I don't know why this particular file timeouts (I never has issues with the others).

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