3 ms·
All I know is he tried pushState. Perhaps replaceState is not throttled, because it doesn't create new history entries, just replaces the last one. Try this in
by megous 8y ago
All I know is he tried pushState. Perhaps replaceState is not throttled, because it doesn't create new history entries, just replaces the last one.
Try this in chrome console. And yes, it doesn't throttle at all.
i=0; setInterval(() => history.replaceState('', '', '/' + (i++)), 50);
It's interesting how people will just believe everything, even if the test is 30 seconds away.
- eridius 8y agoI just tested, Safari still throttles history.replaceState().
- addicted 8y agoI'm pretty sure Chrome has different behavior with Dev Tools open and Dev Tools closed, and also with what it does with code posted in the console and code run as part of the page. So just because it is not throttled when run in the console doesnt necessary imply it wont throttle as part of a regular page as well.
- megous 8y agoIt does not in this case. It's just not throttled.
- bspammer 8y agoI tried this and it still seems to flood my browser history. I can use the back button properly now though.