pushState() and navigations and history navigation rate limiting no longer throws
- Dominant language
- Markdown
- Stars
- 11k
- Forks
- 23.2k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 331
Description
### MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/History/pushState
### What specific section or headline is this issue about?
https://developer.mozilla.org/en-US/docs/Web/API/History/pushState#exceptions
### What information was incorrect, unhelpful, or incomplete?
Says that a SecurityError exception is thrown "if the method is called too frequently".
### What did you expect to see?
This may still apply for some browsers for a bit, but the spec change it to instead return (no-op) upon rate limiting, which is what Chromium currently does and Gecko will soon do.
### Do you have any supporting links, references, or citations?
https://github.com/whatwg/html/pull/12492
### Do you have anything more you want to share?
Also applies to replaceState, history.go/back/forward, `navigation` API and APIs that navigate (e.g. `location.href`).
### MDN metadata
Page report details
* Folder: `en-us/web/api/history/pushstate`
* MDN URL: https://developer.mozilla.org/en-US/docs/Web/API/History/pushState
* GitHub URL: https://github.com/mdn/content/blob/main/files/en-us/web/api/history/pushstate/index.md
* Last commit: https://github.com/mdn/content/commit/3e543cdfe8dddfb4774a64bf3decdcbab42a4111
* Document last modified: 2025-06-23T16:41:39.000Z
Contributor guide
Assessment
This issue has not been assessed yet.