259637 2023-07-30 14:41:01 -0700 Unable to use OPFS in web extension because of changing origin 2023-08-06 14:41:12 -0700 1 1 1 Unclassified WebKit WebKit Extensions Safari 16 All All NEW InRadar P2 Normal --- 1 olegwock webkit-unassigned timothy webkit-bug-importer oldest_to_newest 1968799 0 olegwock 2023-07-30 14:41:01 -0700 I'm porting my Web Extension to Safari. This extension has a feature where user can upload images which later can be used in the extension. In chrome/firefox I currently use OPFS (https://webkit.org/blog/12257/the-file-system-access-api-with-origin-private-file-system/) to store icons. But because Safari changes extension's origin on every browser restart, extension can't utilize OPFS, since it will lost access to it after browser restart (which makes it unusable for persisting data). This is a bit related to this bug https://bugs.webkit.org/show_bug.cgi?id=244330 In a way that it's caused by same thing I assume origin is changed on every run to resist fingerprinting, so making it stable probably isn't a feasible solution. But can we have some alternative way to use OPFS in web extension? For example, webkit can use extension id (`browser.runtime.id`) as origin to persist OPFS between runs? 1968804 1 olegwock 2023-07-30 15:47:14 -0700 After a bit more searching I found mention from Timothy Hatcher (https://github.com/w3c/webextensions/blob/main/_minutes/2023-05-11-wecg.md) that Safari currently migrates DOM Storage when origin changes. So my initial proposal (to use extension id as origin) doesn't make much sense anymore, as there is already established solution for this kind of problem (just for other storage types). If we could get same treatment form OPFS that would be awesome 1969869 2 webkit-bug-importer 2023-08-06 14:41:12 -0700 <rdar://problem/113473959>