<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Remove arbitrary limit on pushState and replaceState"
href="https://bugs.webkit.org/show_bug.cgi?id=156115">156115</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Remove arbitrary limit on pushState and replaceState
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>Safari 9
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Major
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>History
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>james.keane@flipp.com
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=275427" name="attach_275427" title="Chat example - must be served over http for security restrictions">attachment 275427</a> <a href="attachment.cgi?id=275427&action=edit" title="Chat example - must be served over http for security restrictions">[details]</a></span>
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 (<a href="https://trac.webkit.org/changeset/198687">https://trac.webkit.org/changeset/198687</a>) in #155901.
I can find no reasonable justification for diverging from the spec (<a href="https://html.spec.whatwg.org/multipage/browsers.html#the-history-interface">https://html.spec.whatwg.org/multipage/browsers.html#the-history-interface</a>). 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: <a href="http://bl.ocks.org/jameskeane/raw/e0b145e6287b3f12f5e47e6b1d313308/">http://bl.ocks.org/jameskeane/raw/e0b145e6287b3f12f5e47e6b1d313308/</a> also fails and is less easily coalesced.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>