Feature description: Signature-based Resource Loading Restrictions
Eng owner: vogelheim@, mkwst@
Product owner:
Design doc:
https://github.com/w3c/webappsec-subresource-integrity/blob/master/signature-based-restrictions-explainer.markdown
Are you planning on experimenting before launch? Yes.
Any new strings? No.
Any implications for Google webservices (i.e. sync, translate)? No.
Binary size? Likely tiny.
Do the existing perf tests exercise all aspects of your new feature(s)? No.
This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.
We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.
For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit
For any questions, please contact owencm, sshruthi, larforge
Comment 1 by vogelheim@chromium.org
, Aug 9 2017