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

[bugzilla-daemon at webkit.org]

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

--- Comment #4 from James Keane <james.keane at flipp.com> ---
(In reply to comment #3)
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. 
> WebKit cannot possibly know when the page is about to "fake navigate" via a pushState.
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?

-- 
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/20160405/c4885654/attachment-0001.html>