<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><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#c4">Comment # 4</a>
on <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">bug 156115</a>
from <span class="vcard"><a class="email" href="mailto:james.keane@flipp.com" title="James Keane <james.keane@flipp.com>"> <span class="fn">James Keane</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=156115#c3">comment #3</a>)
You've convinced me, that the spec is flexible enough to allow user agents to impose limits on unreasonable usage. I will concede that it is on your authority to define what is and what isn't 'unreasonable' based on, as Section 2.2.1 calls it, 'implementation-specific limits'.
Brady, I would also like to personally apologize, if my initial tweets offended you; I was frustrated at what, at the time, I believed was a spec violating change causing hundreds of thousands of users to see a completely broken site.
I will leave it to you to decide whether throwing a QuotaExceededError, or as the spec _suggests_ ignoring calls is the preferred behaviour; my opinion is the latter.
Either way, I think we can both agree that finding a solution which is not subject to these limits is preferable.
<span class="quote">> WebKit cannot possibly know when the page is about to "fake navigate" via a pushState.</span >
It can, and it is definitely *not* a halting problem; it knows when the page is about to fake navigate, as it knows when pushState is called.
Again, not knowing the specifics, how could 'replaceState' create an OOM situation? Is it not deallocating the previous state object?</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>