Add sanitization of XFBML raw embeds into amp-facebook - #5506
Draft
westonruter wants to merge 1 commit into
Draft
Conversation
[ci skip]
This file contains hidden or 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
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
I'm just opening this PR as a potential starting point for converting
<fb:post>into<amp-facebook>, wherefb:postis the XFBML version of what Facebook now has replaced withdiv.fb-post. Jetpack was usingfb:postwhich is why this issue was discovered, but I've opened Automattic/jetpack#17492 to update Jetpack to usediv.fb-postinstead. Once that is released, this PR should be very low priority since XFBML is not the current best practice.Checklist