On Thu, Nov 20, 2025 at 10:58 PM Mike Taylor <[email protected]> wrote:
> > On 11/20/25 3:04 a.m., Chromestatus wrote: > > *Contact emails* > [email protected] > > *Specification* > > https://html.spec.whatwg.org/multipage/nav-history-apis.html#shared-history-push/replace-state-steps > > *Summary* > Calling pushState/replaceState more than 200 of times/second would throw > an exception instead of failing silently. This aligns with existing Gecko & > WebKit behavior. > > Is there a plan to specify this (interoperable) behavior? After step 10, > HTML talks about implementation-defined limits, but not about throwing > Yes! This change is a part of that effort, which Mozilla is driving. See https://github.com/whatwg/html/issues/11844. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYZtTOUh%3DbDGOSGbZfRBdBXyGE5yHF8Zy6F8ermj%2BSGVTw%40mail.gmail.com.
