- pushState is only used for overriding the default behavior, mostly to keep the url bar in sync with changing client state
- pushState pollutes the browsers history
- users have a mental model of how many steps/clicks they performed on a site and expect that an equal number of clicks on the back button brings them back to the beginning
- users are upset if that expectation is not matched
The site should not have control over the users history in the first place but for SPA it's necessary to achieve the expected behavior. But the browser should make sure that it's not misused. In the same way that pop-ups are blocked outside of whitelisted event listeners to prevent a website from polluting your screen, pushState should be blocked to prevent history pollution.