Hi guys, I'm working on porting an extension to safari-web-extension, and seeing that any content I load inside an iframe on the extension managed new tab page has its storage partitioned due to ITP.
By comparison, on Firefox, at least on the new tab page, iframes do not have their storage partitioned.
Even if we get storage permission by prompting the user using Storage Access API, it would get revoked on the next browser launch since the GUID of the new tab page would be refreshed by Safari.
Is there a workaround for this, or alternatively can we ensure that storage access permission is origin agnostic at least on the new tab page for Safari web extensions?
Keeping it strictly against the origin would not make sense for new tab page in any case since the browser will keep refreshing the page origin on every launch.