2 ms·

It shouldn't. It uses history.replaceState(). https://developer.mozilla.org/en-US/docs/Web/API/History_API#The_replaceState()_method https://developer.mozilla.o

• alangpierce 7y ago
  It actually just updates window.location.hash instead, which does cause a flood of history entries (looks like just one per distinct animation state, though, at least in Chrome). See the "One Last Thing" section near the bottom of the article for the rationale. See the inline code snippets in the article, or view source for wavyurl.com to see the actual code used.
  • eridius 7y ago
    At least in Safari, history.replaceState() still pollutes the browser history, all it does is avoid breaking the back button.