3 ms·
It's pretty awesome! One thing I noticed is that it breaks the browser back button. I see you have some sort of coordinates in the URL, however changing these d
by jameswyse 14y ago
It's pretty awesome! One thing I noticed is that it breaks the browser back button. I see you have some sort of coordinates in the URL, however changing these doesn't seem to do anything?
- SenorWilson 14y agoThey do if you refresh the page, but doing something like this is a nightmare because it floods your browsing history with useless junk. This should be changed immediately.
- dilipray 14y agoIt's amazing. He should work on the coordinates but they worked for me on refresh( onPageLoad ), but i think it should be GET request rather than Hash request
- troels 14y agoYou wouldn't want to actually issue a new request each time the view is updated. A good solution would probably be to use `pushState` on browsers that support it and fall back to the current behavior for older browsers.
- andrewmunsell 14y agoYeah, it essentially is storing a massive number of history items (seems to update the URL too much) and therefore you can never really go back to the previous page if you've scrolled around a lot...
- davecardwell 14y agoPerhaps use history.replaceState() instead of history.pushState() so it doesn’t create a new distinct entry each time, but you still get a URL you can bookmark or share with others? https://developer.mozilla.org/en-US/docs/DOM/Manipulating_the_browser_history#The_replaceState().C2.A0method https://developer.mozilla.org/en-US/docs/DOM/Manipulating_th...
- peterbe 14y agoThe updating of the location hash has now been fixed.