pushState() and navigations and history navigation rate limiting no longer throws

[zcorpan]

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?

whatwg/html#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: 3e543cd
• Document last modified: 2025-06-23T16:41:39.000Z

[hamishwillee]

1. Is there a Firefox / Chrome issue indicating the version in which things changed?
2. When is that PR likely to go into the spec?
3. Are there any particular conditions under which we know a no op will occur? The current text is "if called to frequently" but the removed spec text was a little more indicative: the user agent might disallow calls to these methods that are invoked on a timer, or from event listeners that are not triggered in response to a clear user action, or that are invoked in rapid succession.

This is technically a behavioural compatibility issue - not sure if we need to record it in the compatibility data.