[Webkit-unassigned] [Bug 259637] New: Unable to use OPFS in web extension because of changing origin

[bugzilla-daemon at webkit.org]

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

            Bug ID: 259637
           Summary: Unable to use OPFS in web extension because of
                    changing origin
           Product: WebKit
           Version: Safari 16
          Hardware: All
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Extensions
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: olegwock at gmail.com
                CC: timothy at apple.com

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?

-- 
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/20230730/782d002f/attachment.htm>