Revert require-sri-for
#82
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
hmm this makes me sad too. We use it at Dropbox a lot too. Can you say more whats the reason its causing so much pain? |
|
welp .. just saw your other messages on how this ship's already sailed. |
|
Can you post some references why it was done to better understand reasons of this removal for outsiders? |
|
Thank you for asking. I should have made the pointer earlier. Please see this thread on the webappsec working group mailing list for more information. The mailing list is public and open for further commentary, so let's move all discussion there. |
vincentbernat
added a commit
to vincentbernat/vincent.bernat.ch
that referenced
this pull request
Jul 5, 2019
It is being removed from Firefox and planned to be removed from Chromium. It seems the main reason is that it doesn't cover all scripts/styles and therefore provide a false sense of security and may break in the future. See <w3c/webappsec-subresource-integrity#82>.
sideshowbarker
added a commit
to w3c/browser-compat-data
that referenced
this pull request
Dec 25, 2019
In w3c/webappsec-subresource-integrity#82, the require-sri-for feature was dropped from the spec. So this change updates its BCD status to "standard_track": false, "deprecated": true
sideshowbarker
added a commit
to w3c/webappsec-csp
that referenced
this pull request
Dec 25, 2019
w3c/webappsec-subresource-integrity#82 removed `require-sri-for` from the SRI spec.
queengooborg
pushed a commit
to mdn/browser-compat-data
that referenced
this pull request
Dec 25, 2019
In w3c/webappsec-subresource-integrity#82, the require-sri-for feature was dropped from the spec. So this change updates its BCD status to "standard_track": false, "deprecated": true
This was referenced Jan 3, 2020
annevk
pushed a commit
to w3c/webappsec-csp
that referenced
this pull request
Nov 5, 2020
w3c/webappsec-subresource-integrity#82 removed `require-sri-for` from the SRI spec.
annevk
pushed a commit
to w3c/webappsec-csp
that referenced
this pull request
Nov 5, 2020
w3c/webappsec-subresource-integrity#82 removed `require-sri-for` from the SRI spec.
ryandel8834
added a commit
to ryandel8834/WebAppSec-CSP
that referenced
this pull request
Aug 13, 2022
w3c/webappsec-subresource-integrity#82 removed `require-sri-for` from the SRI spec.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I really liked the feature. 😢
However, we ended up unshipping in Gecko and IIRC @mikewest considered removing from Blink, so I'm making an attempt at removing
require-sri-for.Preview | Diff