Bug 164469

Summary: Web Automation: don't disable localStorage for ephemeral sessions that are being controlled by automation
Product: WebKit Reporter: Blaze Burg <bburg>
Component: Web InspectorAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: andersca, bburg, beidson, darin, inspector-bugzilla-changes, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: All   
OS: All   

Blaze Burg
Reported 2016-11-06 19:38:14 PST
.
Attachments
Blaze Burg
Comment 1 2016-11-06 20:49:08 PST
Brady Eidson
Comment 2 2016-11-07 09:15:55 PST
Ephemeral sessions should *not* use the storage backend that actually stores to disk. So this bug is, by necessity, more than just "don't disable localStorage for ..." We'll need a mode for localStorage to use an in-memory backing store.
Blaze Burg
Comment 3 2016-11-07 09:52:31 PST
(In reply to comment #2) > Ephemeral sessions should *not* use the storage backend that actually stores > to disk. > > So this bug is, by necessity, more than just "don't disable localStorage for > ..." > > We'll need a mode for localStorage to use an in-memory backing store. Does such a backing store already exist? It seems sketchy to me that the file-based backend is hooked up to ephemeral sessions right now, and we rely on this check to prevent code from actually using it.
Brady Eidson
Comment 4 2016-11-07 10:11:09 PST
(In reply to comment #3) > (In reply to comment #2) > > Ephemeral sessions should *not* use the storage backend that actually stores > > to disk. > > > > So this bug is, by necessity, more than just "don't disable localStorage for > > ..." > > > > We'll need a mode for localStorage to use an in-memory backing store. > > Does such a backing store already exist? Yes - sessionStorage uses a per-WebView, in-memory backing store. And that's exactly what we'll want to use for localStorage in a WebView whose storage session is ephemeral.
Blaze Burg
Comment 5 2017-05-18 11:52:42 PDT
This bug is no longer needed.
Note You need to log in before you can comment on or make changes to this bug.