Framework: Pin fetch polyfill to 3.0 UMD distributable #9795
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
aduth
added
[Type] Bug
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.
This should be included in a 3.8 final release.
This pull request seeks to resolve an issue where the
fetchpolyfill is no longer usable in Internet Explorer 11. This was due to the fact that we had never pinned the version of polyfill we consume, thus when its latest 3.0.0 release included breaking changes to the default build targetting JavaScript modules, not supportable in IE11.The changes here target the IE-compatible UMD build, and also pin to the 3.0.0 version to avoid future issues.
Testing instructions:
Verify that saving works as expected in Internet Explorer and your preferred browser.
Based on our hashing of vendor scripts, I do not expect that an existing downloaded/cached copy should need to be deleted.