[Webkit-unassigned] [Bug 231879] No IndexedDB persisted for iframe on different subdomain / port

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Oct 18 00:23:28 PDT 2021


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

--- Comment #5 from mail at getflourish.com ---
I’m trying to understand wether this is a bug or expected behaviour related to ITP:

What I see happening is related to "Partitioning" and "Ephemeral". But after reading about tracker prevention I don’t understand why my case (same site, different subdomains) are treated like Third-Party (?)

---

From: https://webkit.org/tracking-prevention/

> **Partitioning** is a technology to allow third-parties to use storage and stateful web features, but have those isolated per first-party website. 

> **Ephemeral.** When we say ephemeral storage, we mean the storage does not persist to disk and goes away with the application, for instance when the user quits the browser or reboots their device. 

→ This is what happens.

> **Third-party** LocalStorage and IndexedDB are partitioned per first-party website and also made ephemeral.

---

I’ve also read the article about the updates to the storage API. https://webkit.org/blog/11545/updates-to-the-storage-access-api/

I can confirm that the iframe returns "false" for document.requestStorageAccess(). I can call document.requestStorageAccess() after user interaction and then document.requestStorageAccess() returns "true". 

But if I restart Safari, we’re back at zero.

-- 
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/20211018/45562aab/attachment.htm>


More information about the webkit-unassigned mailing list