REST API: Remove oEmbed proxy HTML filtering #13575
Merged
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.
Related: https://github.com/WordPress/gutenberg/pull/9734/files#r252005662
Related: #13408
This pull request seeks to remove Gutenberg's filtering of the oEmbed proxy endpoint responsible for filtering HTML from the response. This was implemented as part of the following Trac ticket and corresponding changeset:
Per #9734, the function serves a secondary purpose of handling a failing oEmbed proxy request which could be handled as a shortcode. This was never merged as part of the WordPress 5.0 release, and thus has been left as an extension provided by Gutenberg. The task to bring this in core can be found at the following link:
In the meantime, the function
gutenberg_filter_oembed_result
has been paired down to include only this specific handling.Testing instructions:
Repeat testing instructions from #9734