Ensure BrowserContext::SaveSessionState preserves all storage types |
|||
Issue descriptionBrowserContext::SaveSessionState is called to override the behavior of "clear on exit" / session-only storage for all or particular origins, when a "session" is not really a session (e.g. Android app termination) This is hooked up for cookies, WebSQL, DOM Storage, and Indexed DB by calling into the appropriate context and setting a flag. It looks like this is not hooked up for filesystem, cache storage, service workers, and potentially other types.
,
Oct 18
Tests are in chrome/browser/sessions/better_session_restore_browsertest.cc but don't cover most of the storage types.
,
Oct 18
,
Oct 19
https://cs.chromium.org/chromium/src/chrome/browser/browsing_data/browsing_data_remover_browsertest.cc?l=1100&rcl=394e487383529b54c0f09d1a2fb0dcca79654bc2 There is a ClearOnExit test here that is capable of covering all data types. We could make a version that sets BrowserContext::SaveSessionState to check if data is kept. |
|||
►
Sign in to add a comment |
|||
Comment 1 by jsb...@chromium.org
, Oct 18