Missing worker integration

[annevk]

I realize that Storage Access itself isn't properly sorted out around workers though we do have a plan of sorts, if I remember correctly. However, it seems that this specification doesn't address them at all. Just like documents have subresources, workers do too. I could see not handling style sheets as having subresources, but since workers create their own environments I think they probably need to be handled in some fashion?

[johannhof]

We should probably discuss Storage Access and workers again, including this question. @annevk do you have time for the next PCG call in 2 weeks?

[annevk]

I'm out the week of February 3, if that's the week you mean.

[johannhof]

Ah, that's good to know, thanks. Maybe we should skip this discussion to the call after next, then? cc @privacycg/chairs

[cfredric]

Thanks Anne, would love some help on workers. I kept the SAH spec in terms of environment settings objects since the request's client is an ESO whose global object might be a WorkerGlobalScope, or Window, etc. So in theory SAH should "just work" with documents, workers, and worklets, assuming that other specs all handle all kinds of ESOs well. In practice I know that some other specs need to be updated to properly consider workers (e.g. Storage Access itself, Permissions, ...) and maybe SAH needs to use task sources differently, so there's likely followup we ought to do.

[annevk]

SAH specifically integrates with "navigate", but nothing is done for worker environment creation. Normally we'd try to treat the main worker resources in much the same way we treat documents.

[cfredric]

Aha, the integration with "navigate" is specifically for the Activate-Storage-Access: load header processing. Maybe we can make that header apply when creating dedicated workers as well, good point. (Shared workers and service workers are more complicated, I don't know if we can extend the header to support those types. https://github.com/privacycg/saa-non-cookie-storage might be our best fallback for shared workers.)

[sandormajor]

We discussed this with Chris a couple weeks ago so just adding it here as a reminder to ourselves. Permissions Policies are also not working with Workers/Worklets: https://w3c.github.io/webappsec-permissions-policy/#issue-4ecdbcc2