Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing worker integration #26

Open
annevk opened this issue Jan 21, 2025 · 6 comments
Open

Missing worker integration #26

annevk opened this issue Jan 21, 2025 · 6 comments
Labels

Comments

@annevk
Copy link

annevk commented Jan 21, 2025

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
Copy link
Member

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
Copy link
Author

annevk commented Jan 24, 2025

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

@johannhof
Copy link
Member

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

@cfredric
Copy link
Collaborator

cfredric commented Feb 7, 2025

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
Copy link
Author

annevk commented Feb 10, 2025

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
Copy link
Collaborator

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.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants