[N/A] SVG Support Removal #155
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
|
@nevinsm When you get a moment, I want to draw your attention to the changes in this file. I am removing the GitHub |
|
@bd-viget That looks fine to me. If anyone wants to use it they can always just go grab it from this repo. |
nevinsm
approved these changes
Oct 16, 2024
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.
Summary
This PR eradicates SVG Support and replaces it with Safe SVG. This was supposed to be in the last PR, however, something weird happened with the
composerfile (maybe a bad merge), and it still remained.Issues
I just realized some of this work is duplicated in this PR, but this solution is a bit more robust, and cleans up some WP Site Starter specific GitHub files.
Testing Instructions