229811 2021-09-02 09:30:03 -0700 Implement Storage API 2023-05-10 14:54:01 -0700 1 1 1 Unclassified WebKit New Bugs WebKit Nightly Build Unspecified Unspecified NEW InRadar P2 Normal --- 229925 229965 230053 230059 230675 248918 1 sihui_liu webkit-unassigned dvpdiner2 nbrustein sihui_liu webkit-bug-importer oldest_to_newest 1789737 0 sihui_liu 2021-09-02 09:30:03 -0700 Spec: https://storage.spec.whatwg.org 1789738 1 webkit-bug-importer 2021-09-02 09:30:40 -0700 <rdar://problem/82678873> 1908979 2 gsnedders 2022-10-28 05:00:44 -0700 AFAICT, the only thing left to do here is https://github.com/WebKit/WebKit/blob/a121340322ef72e3e303af58db1c88cb23bf397d/Source/WebCore/Modules/storage/StorageManager.idl#L36 : // FIXME: add Promise<StorageEstimate> estimate(); That said, we don't appear to have any open bug for that? 1942540 3 nbrustein 2023-03-20 07:27:16 -0700 I'm not seeing StorageManager.persist() and persisted() work in the way I expect. Here is what I'm seeing in Safari: * storage.persist() will resolve to true * In the same session, storage.persisted() will resolve to true * After refreshing the page storage.persisted() will resolve to false I would expect that if storage.persisted() resolved to true in one session, it would still be true in a subsequent session. That's what I'm seeing in Chrome and FF. Am I misunderstanding the behavior here, or is this unexpected? 1954527 4 sihui_liu 2023-05-10 14:54:01 -0700 (In reply to Nate Brustein from comment #3) > I'm not seeing StorageManager.persist() and persisted() work in the way I > expect. > > Here is what I'm seeing in Safari: > > * storage.persist() will resolve to true > * In the same session, storage.persisted() will resolve to true > * After refreshing the page storage.persisted() will resolve to false > > I would expect that if storage.persisted() resolved to true in one session, > it would still be true in a subsequent session. That's what I'm seeing in > Chrome and FF. > > Am I misunderstanding the behavior here, or is this unexpected? Hi, the persisted flag was not persisted (as WebKit didn't evict data on storage pressure), and this particular issue is fixed at https://bugs.webkit.org/show_bug.cgi?id=256483.