134692 2014-07-07 13:47:41 -0700 Add API for saving and restoring a WKWebView's _WKSessionState 2020-07-06 02:56:25 -0700 1 1 1 Unclassified WebKit New Bugs 528+ (Nightly build) Unspecified Unspecified NEW InRadar P2 Normal --- 1 andersca andersca beidson benjamin danyao dieter fpatel ivan.hantov kc martijn sam stefan webkit-bug-importer oldest_to_newest 1020896 0 andersca 2014-07-07 13:47:41 -0700 Add API for saving and restoring a WKWebView's _WKSessionState 1094153 1 stefan 2015-05-12 07:00:25 -0700 Would this state also include the WKBackForwardList ? 1101447 2 webkit-bug-importer 2015-06-11 16:44:18 -0700 <rdar://problem/21349869> 1158660 3 beidson 2016-01-25 18:54:06 -0800 (In reply to comment #1) > Would this state also include the WKBackForwardList ? Yes, it would. 1317054 4 ivan.hantov 2017-06-08 14:27:43 -0700 It would (In reply to Brady Eidson from comment #3) > (In reply to comment #1) > > Would this state also include the WKBackForwardList ? > > Yes, it would. Please do fix this. Or at least make the backForwardList readwrite. It is now impossible to restore the state of the WKWebView when the app starts. There's many proposed hacks, but none works really well. 1669011 5 martijn 2020-07-06 02:56:25 -0700 I hope this is the right issue to revive discussion around session state restoration for WKWebView. I recently asked Brady Eidson about exposing the existing private _WKSessionState API on Twitter, and he mentioned more work would be needed to design a better API for this (https://twitter.com/bradeeoh/status/1278359540551933952?s=20): > Hi! We know developers have uses for this type of API, and as such it's on our roadmap. > It's not nearly as simple as exposing that SPI, which is *not* something we're proud of and would dread supporting in perpetuity. Not sure what the right process for this is, but I'd love to find a way to help make progress on this issue. Since this seems to be a long standing issue and I'm new to the project, I'm sure there's a lot of context I'm missing. What problems with the existing API have kept it from being made public? What direction are people thinking in for redesigning it?