[Webkit-unassigned] [Bug 156115] New: Remove arbitrary limit on pushState and replaceState

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=156115

            Bug ID: 156115
           Summary: Remove arbitrary limit on pushState and replaceState
    Classification: Unclassified
           Product: WebKit
           Version: Safari 9
          Hardware: All
                OS: All
            Status: NEW
          Severity: Major
          Priority: P2
         Component: History
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: james.keane at flipp.com

Created attachment 275427
  --> https://bugs.webkit.org/attachment.cgi?id=275427&action=review
Chat example - must be served over http for security restrictions

An arbitrary 100 maximum calls to 'pushState' and 'replaceState' was recently added to WebKit, which I have been informed was recently softened to 100 calls per 30 second interval (https://trac.webkit.org/changeset/198687) in #155901.

I can find no reasonable justification for diverging from the spec (https://html.spec.whatwg.org/multipage/browsers.html#the-history-interface). I assume it is related to "crashsafari.com", but I am "not authorized" to view the ticket (#153435) which introduced this change.

I was asked on twitter by @beidson, how 3 updates per second is not enough; my use case is updating scroll state at 60fps, but this example of a chat app: http://bl.ocks.org/jameskeane/raw/e0b145e6287b3f12f5e47e6b1d313308/ also fails and is less easily coalesced.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160401/26f6cdd9/attachment.html>