-
Notifications
You must be signed in to change notification settings - Fork 143
[worklets] Provide hook for allowing downstream specs to specify a CSP destination. #378
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
Labels
Comments
bfgeek
added a commit
that referenced
this issue
Apr 7, 2017
Fixes #92. (better late than never? ;) Broadly speaking worklets should be allowed in non-secure contexts as downstream specs may want to use them there. CSP wise this should work the same as workers, using the "child-src" directive. I've filed issue #378 to allow each downstream spec to use a unique destination, e.g. "paintworklet", "audioworklet", etc. The CSP spec should probably be extended to have a "worklet-src" directive (as there is now a "worker-src" directive now?).
bfgeek
added a commit
that referenced
this issue
Apr 13, 2017
Closed
Sent whatwg/fetch#527 for fetch integration. |
And sent w3c/webappsec-csp#205 for CSP integration. |
What is preventing this to be merged, @bfgeek ? The two PRs above are merged. |
@padenot Done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For example the css-paint-api spec should provide its worklet with a destination of "paintworklet".
Being more granular probably makes more sense here, instead of just a generic "worklet" destination.
The text was updated successfully, but these errors were encountered: