Pin playground to v1.7.28 and add polyfill for mutation events #1159
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.
Apparently 'mutation events' like DOMNodeRemoved were removed from Chrome this past July. Meanwhile, Playground hasn't had an update in years. This PR adds a polyfill for the removed functionality so that the obsolete Playground UI will continue to function.
In addition, I added subresource integrity hashes to the scripts. This is to prevent users from becoming susceptible to hackers if the CDN is compromised, such as occurred recently in this news article:
Browsers will reject the script if it doesn't match the SHA-384 hash embedded in our html page, preventing compromise of their server.
Since all scripts now have their content checked to match a predetermined hash, the exact version of the npm package was added to the links. Otherwise, if a newer version is released, Playground would not load since the hash would not match.
Closes:
See: