[Webkit-unassigned] [Bug 169618] WKWebView does not allow saving and restoring WKBackForwardList

[bugzilla-daemon at webkit.org]

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

--- Comment #5 from Stefan Arentz <stefan at arentz.ca> ---
I assume Eugene is asking for the same reason that the Firefox for iOS team is also exploring this API today:

iOS 11 has severely regressed WebKit rendering: we are getting lots and lots of reports of users who are only seeing half rendered pages. On both iPad and iPhone. With both 1 tab and multiple tabs.

This is reported / docuemnted at:

 - https://bugs.webkit.org/show_bug.cgi?id=179885
 - rdar://problem/35657388
 - https://bugzilla.mozilla.org/show_bug.cgi?id=1416849
 - https://bugs.chromium.org/p/chromium/issues/detail?id=774452

The workaround for this regression is to completely deallocate the WKWebView and then put a new instance in the view hierarchy.

This of course loses all state, so we too are exploring if NSCoding support is good enough for this workaround.

Both Chrome and FIrefox have super hacky workarounds in place for back forward list saving / restoring.

I hope this background is useful to give some insight in the sudden interest in this functionality.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20171130/292df9c4/attachment.html>