Specify a suggested limit for repeated `replaceState()` calls

[zcorpan]

What is the issue with the HTML Standard?

In https://bugzilla.mozilla.org/show_bug.cgi?id=1995636 Firefox ran into a web compat issue due to replaceState() throwing after reaching the UA-defined limit of repeated calls. I think Gecko's current limit is 200 replaceStates (or location.hash changes; see #11410) in 10 seconds.

WebKit's limit is 100. Chromium's limit is 200, but after that it no-ops instead of throwing.

We're considering increasing the limit to 1000. If there's interest in aligning on the number we can codify it in the spec.

[annevk]

Does increasing the limit meaningfully improve the experience of end users? It sounds like resource abuse to me. If not throwing works when the limit is reached that seems like a much more practical solution.

cc @beidson