window.history attribute named
pushState() which allows developers to store an object, a title, and a URI representing the current page where the URI can change the fragment, query and path part of the URI (and nothing else). Pretty neat!
This is really great! But I think there is also a use case for replaceState, or a count argument with clearState. There are cases where you want to update the current state in the history, instead of adding a new state: for example if you are navigating around a map, like Google maps.
You don't want to remove all the state objects, like clearState does. Take f.e. Google Maps again: you want searches to add to the history, and they should not disappear from history if you navigate the map.
Put in other words, we want
window.history.replaceState, just as there is
Really great news. Just hope not everybody does like Kudos and use AJAX for displaying the main content.