4 ms·
Changing the hash, and therefore the URL, adds a new entry to your history. Lots of sites, even popular ones (looking at you, Skydrive) does abuse this and ruin
by pestaa 13y ago
Changing the hash, and therefore the URL, adds a new entry to your history. Lots of sites, even popular ones (looking at you, Skydrive) does abuse this and ruins the browsing experience. I have to remember which sites are implemented this way and keep those on separate tabs.
- jawr 13y agoAh it's the fragments that are causing this. Thanks for the info. Would be nice if the back button wasn't default based to fragments but actual URLs (fragments don't get sent to the server, right?).
- kirchhoff 13y agoIt's possible to avoiding creating history entries by using location.replace()
- pestaa 13y agoFragments indeed don't get sent to the server, and are usually used to track your location inside the document (be it jumping to section headers, or using js-generated dialog boxes, etc.). In an ideal world, this fragment is not changed unless the user explicitly changes the state. Unfortunately, apps often use it to store their own state.